OWC and execution location at the server side bad performance (sometimes)??? -
08-17-2005
, 10:05 AM
Hi,
I'm surprise to see bad performance results when I setup my connection
string to execute the query at the server side instead-of client side.
my measure is a calculated one in a virtual cube which calculate a ratio
between 2 measures of 2 cubes (simple sum measures).
if I execuite it at the client side the response time is 2 seconds.
at the server side... the same access takes 3 to 4 minutes!!!!!
client side version:
Provider=MSOLAP.2;Persist Security Info=False;Data
Source=<servrname>;Initial Catalog=<database>;Client Cache Size=25;Auto
Synch Period=10000;Cache Policy=7;MDX Compatibility=2;MDX Unique Name
Style=3;Cache Ratio=0.001;Non Empty Threshold=1;Cache Ratio2=0.001
for server side mode, I add these parameters:
Execution Location=3;Default Isolation Mode=1;
this connection string is required for my distinct count formula. these
parameters improve the performance for this type of calculation.
Does these parameters break the performance for "standard" usage like my
ratio?
why in server side mode, the system takes so many times?
thanks.
Jerome. |