Useage Based Optimization Connection String
-
3. prosince 2009 15:27I tried to start the Usage Based Optimization wizard and got a warning message that states:
An OLE DB Provider was not specified in the ConnectionString. An example would be, 'Provider=SQLOLEDB;'.
All of the filter criteria are greyed out and I can not continue. I suspect that it is looking at the Log\QueryLog\ConnectionString property of the Analysis Services instance. Is this the case?
Assuming it is, ours is encrypted and so I would guess that was the problem. I would greatly appreciate any practical advice on how to handle this.
Všechny reakce
-
3. prosince 2009 15:49it is reading the ConnectionString property. I have run into this issue as well but I am not sure what causes it. Typically I go into the AS properties and redefine the connection string.
FJK -
3. prosince 2009 17:06So essentially you put the connection string in unencypted, run the UBO wizard and then reencrypt the string?
-
3. prosince 2009 18:42it encrypts itself
FJK -
17. března 2012 2:28
I encountered the same issue. The Query Log table Connection String in the SSAS server property is auto-encrypted, so that the Usage Based Optimization (UBO) is not able to access the content in this table.
However it looks like the queries made to the cube are still continuously being logged into the Query Log table. Any idea?
Thanks.