How to: Define a Remote Partition

How to: Define a Remote Partition

SQL Server 2005

Two separate computers that are running a single instance of SQL Server 2005 Analysis Services (SSAS) are each required to create a remote partition arrangement that designates one computer as the master server and the other computer as the subordinate server.

To create a remote partition arrangement, you must have OLAP Administrator status on both computers, and the firewall settings on the master server computer must be set to accept outside connections. For information about setting the firewall, see How to: Configure Windows Firewall for Analysis Services Access. For more information about using partitions, see Managing Analysis Services Partitions.

  1. On the master server: Create a new project populated with a cube.

  2. On the master server: Right-click the project name in Business Intelligence Development Studio Solution Explorer and select Properties.

  3. On the master server: In the Property Pages dialog box, under Configuration Properties, select Deployment. In the Server name box, type the name of the master server instance of Analysis Services. Click OK.

  4. On the master server: Right-click the project name in Solution Explorer and select Process. Deploy and process your project.

  5. On the subordinate server: Create a new project in Business Intelligence Development Studio with a data source pointing to the master server database. Use the provider Native OLE DB\Microsoft OLE DB Provider for Analysis Services 9.0.

  6. On the subordinate server: Right-click the project name in Solution Explorer and select Edit Database.

  7. On the subordinate server: Under Properties, set the MasterDataSourceID to the newly created master server data source ID.

  8. On the subordinate server: In Solution Explorer, right-click the database name and select Properties. In the Properties dialog box, click Configuration Properties, then click Deployment, and then click Server and set the subordinate server's name.

  9. On the subordinate server: Deploy and process the database.

  10. On the subordinate server: In SQL Server Management Studio, right-click your connected Analysis Services instance in Object Explorer and select Properties. Set both Feature\LinkToOtherInstanceEnabled and Feature\LinkFromOtherInstanceEnabled to true.

  11. On the subordinate server: Restart the server by right-clicking the server name in Object Explorer and selecting Manage Service. In the Service Properties dialog box, click Restart.

  12. On the master server: In SQL Server Management Studio, right-click your connected Analysis Services instance in Object Explorer and select Properties. Set both Feature\LinkToOtherInstanceEnabled and Feature\LinkFromOtherInstanceEnabled to true.

  13. On the master server: To restart the server, right-click the server name in Object Explorer and select Manage Service. In the Service Properties dialog box, click Restart.

  14. On the master server: In Business Intelligence Development Studio, create a new data source in your project, pointing to the subordinate server database. Use the provider Native OLE DB\Microsoft OLE DB Provider for Analysis Services 9.0.

  15. On the master server: Open the cube's Partitions page. Right-click the cube and select Partitions.

  16. On the master server: If you don't already have a table ready to use for the new partition, you must delete an existing partition. To do so, right-click any partition name and select Delete, then add a new partition by clicking the New Partition link.

  17. On the master server: Click through the Partition Wizard until you get to the Processing and Storage Locations page. Under Processing Location, set Remote AS data source to the newly created data source that points to your subordinate database. Complete the wizard.

  18. On the master server: Right-click the cube name in Solution Explorer, select Process and fully process the cube.

Community Additions

ADD
Show:
© 2016 Microsoft