Creating and Managing a Remote Partition
Before you create a remote partition, the following conditions must be met:
- A database dedicated to serving remote partitions for the local database must be created on the remote server.
- The domain user account for the local instance of SQL Server 2005 Analysis Services (SSAS) must have administrative access to the remote instance of Analysis Services.
- In order to create or maintain a remote partition, your user name must also be included in the OLAP Administrators group for both the remote and the local instances of Analysis Services.
The domain user account for the local instance of Analysis Services must have administrative access to the remote database.
You create a remote partition using the Partition Wizard. On the Specify Processing and Storage Options page, for the Remote Analysis Services data source, specify the dedicated database on the remote instance of Analysis Services. This instance of Analysis Services is called the remote server of the remote partition. For Storage location, you can specify the default data location for the remote server or a specified folder on the server.
You must create an Analysis Services database on the remote server and provide appropriate security settings. An additional OLAP data source is created on the remote database pointing to the server on which the partition is defined. The MasterDatasourceID property setting on the remote database points to the data source which, in turn, points to the master server. This property is only set on a database that contains remote partitions. The RemoteDatasourceID property setting on the remote partition specifies the ID of the OLAP data source on the master server that points to the remote server. A remote database can only host remote partitions for a single server.
See Also
Tasks
How to: Define a Remote Partition
Concepts
Creating and Managing Local Partitions
Partitions (Analysis Services)