12.5. Legacy DSO Applications
If you have experience with DSO (object model used for managing Analysis Services 2000), we expect you will find AMO straightforward. The good news is that if you have imported your Analysis Services 2000 database to Analysis Services 2005, you can still make those client apps written for Analysis Services 2000 work. This is accomplished using the version of DSO shipped with Analysis Services 2000 Service Pack 4 along with some additions. We refer to the DSO installed with SQL Server 2005 as DSO8.5. If you have an existing DSO application you will be able to use that application to manage the upgraded or migrated database as long as there has been no changes to the migrated database using SQL Server 2005 tools. The overall architecture showing how an existing DSO application can communicate with Analysis Services 2005 is shown in Figure 12-32.
Figure 12.32. Figure 12-32
When an existing DSO-based application attempts to connect to Analysis Services 2005; DSO8.5 is used to make the connection. DSO 8.5 first tries to connect to Analysis Services 8.0 (Analysis Services 2000), followed by Analysis Services 7.0. When connections to both Analysis Services 8.0 and 7.0 fail DSO 8.5 connects to Analysis Services 2005 through AMO. Repository connection string information and the locks directory are garnered and stored as properties in the Analysis Services ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access