Cache Policy
We are modelling a cube in analysis services 2005 which has custom rollup due to which the performance is very slow. If i use this property cache policy=9 the performance increases a bit.
I tried it in 2 ways:
1. I changed the value of calculation cover policy to 9 in msmdsrv.ini .
2.I added the property cache policy=9 in the connection string
(for example:Provider=MSOLAP.3;Cache Policy=9;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=ABBOTT D 01050 PSO STL ABNEOSA_11299__20080122;Location=localhostsqlserver2005)
My application works fine in the machine that has analysis services 2005 but my application fails to work in the system that doesnt have Analysis services 2005.
Software/Hardware used:
Software/Hardware used:
ASKED:
February 13, 2008 1:40 PM
UPDATED:
February 14, 2008 4:51 AM
RELATED QUESTIONS
- Will cache policy=9 work in system that has MS analysis services 2000 or MS Analysis services 2005.
- SQL 2000 migration to SQL 2005 - need to preserve user security
- Formal description of non-functional properties in SOAs
- Microsoft ISA Server 2000 - Firewall service deliberately stopped - Want to allow ping.
- How do I view a Crystal Report using properties of my object classes.
Answer Wiki:
In SSAS 2000 this setting was introduced in SP3. You may not have SP3 or above installed on both the SSAS 2000 client and server. While it's common to install the SQL Server service packs and hotfixes on the servers, most people forget to install them on machines with just the client tools installed.
To see all answers submitted to the Answer Wiki: View Answer History.
If I am using this Setting is it mandatory to have MS Analysis services 2005 or MS Analysis services 2000 with sp3 in my system?