Databases Reference
In-Depth Information
duction servers is different from those on your test servers. In such a circum-
stance you would need to ensure you secure the database by defining the
right security on production servers. In a circumstance where the backup was
taken on your production server and you are restoring the database on an up-
graded production machine we do expect users to restore the database with
the security information.
Synchronization
Synchronization sounds like a sophisticated, highly technical area of en-
deavor, but actually, it couldn't be simpler; consider synchronization as just
replication for Analysis Services 2005 databases. The name actually is suit-
able because it allows you to "synchronize" the Analysis Services database
resident on an Analysis Services instance to another Analysis Services in-
stance. Typically engineers test the designed Analysis Services database on
a test environment before they move them to their production servers. Engin-
eers often have to backup their database on test servers and restore them on
production servers. However through the synchronization feature in Analysis
Services 2005 engineers can move well tested database(s) from test servers
to production servers with ease.
If you have an Analysis Services instance actively supporting a population of
users, you want to be able to update the database they're querying against
without taking the system down to do so. Using the Synchronize Database
Wizard you can accomplish the database update seamlessly. The wizard will
copy both data and metadata from your development and test machine (sta-
ging server) to the production server and automatically switch users to the
newly copied data and metadata based on conditions defined on production
server. To try this out, you need to have two instance of Analysis Services in-
stalled on another machine, or have a second instance of Analysis Services
installed on your current machine. We recommend you to install another in-
stance called I2 on the same machine. Follow the steps below to synchronize
a database from default instance to the newly instance named instance.
1. Launch SSMS and connect to your default instance (localhost) and
named instance (localhost\I2) of Analysis Services as shown in
Fig-
Search WWH ::
Custom Search