You are a database developer and you have about two years experience in creating
business Intelligence (BI) by using SQL Server2008.
Now you are employed in a company named NaproStar which uses SQL Server2008. There
are two servers in your company.
One is a production server and another one is a development server.
Now you’re in charge of a SQL Server 2008 Analysis Services (SSAS) database on a
production server.
The database has a cube. New functionality has been added to the cube on a development
server.
Now you receive an order from your company CIO, according to the requirement of the CIO,
the new functionality has to be deployed from the development server to the production
server.
You have to accomplish this task and reduce the effect on the users to the least. So what
action should you perform?
A.
In order to accomplish this task, you should copy the appropriate files from the
development server to the production server
B.
In order to accomplish this task, the Synchronize Database Wizard should be used.
C.
In order to accomplish this task, using Business Intelligence Development Studio (BIDS),
modify the Target Server property to the production server. Then deploy the solution
D.
In order to accomplish this task, first the production database should be detached.
Second, you should copy the appropriate files to the production server; at last you should
attach the database on the production server.
Explanation:
p . 287
Using the Synchronize Database Wizard
Synchronizing two SSAS databases is a common management task. For example, you
might need to process a cube once on a dedicated staging server and then deploy it to
loadbalanced production servers. The traditional way to synchronize databases is to back up
and restore the SSAS database, but this requires several steps and might take longer than
you want. Instead, consider simplifying this task by using the Synchronize Database Wizard.
Understanding Database Synchronization The output of the Synchronize Database Wizard is
a single XMLA command named Synchronize. You need to send this command to the target
server whose objects need to be updated. When the target server receives the Synchronize
command, it forwards the command to the specified source server so that the target server
can acquire a read lock on the source database. Next, the target server obtains a list of
source database metadata and data files. Having received the fi les, the target server
releases the read lock on the source database because the target server can complete the
remaining tasks on its own. The target server compares the source fi les against the state of
the target database and identifies the differences. Last, the target server applies the
metadata and data differences to the target database to make it identical to its source
counterpart. IMPORTANT setting up security Because copying the database metadata and
data is a sensitive task, the Windows account under which the target SSAS server runs must
have administrative rights to the source database. When you connect to the source server in
SSMS, you connect under your identity. However, the target server executes the
Synchronize command under its service account. If this is the Local System Windows
account, the command will fail. To avoid this, confi gure the target SSAS server to run under
a domain account and grant that account administrative rights to the source database.
EXAM TIP Suppose that you have a farm of production servers and you need to deploy the
latest changes to each server. you want to avoid processing the SSAS database on eachproduction server because each cube would take very long to process. Instead, you decide
to process the cube on a staging server and then synchronize each production server with
the staging server. The Synchronize Database Wizard is designed specifically to handle this
deployment model.