Administering and Monitoring Analysis Services - SQL Server Analysis Services 2012 Cube Development - page 297

5. The Synchronization wizard allows you to execute synchronization right
away or save the command to a file. You do not have the option of scripting
the command to the query window or clipboard. The Synchronize XMLA
command will look like the following:
<Synchronize xmlns:xsi =
"http://www.w3.org/2001/
XMLSchema-instance" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns
= "http://schemas.microsoft.com/
analysisservices/2003/engine">
<Source>
<ConnectionString>Provider =
MSOLAP.5;Data Source =
julia-pc\sql2012;Integrated Security =
SSPI;Initial Catalog =
AdventureWorks_Sample</ConnectionString>
<Object>
<DatabaseID>AdventureWorks_Sample</DatabaseID>
</Object>
</Source>
<SynchronizeSecurity>CopyAll</SynchronizeSecurity>
<ApplyCompression>true</ApplyCompression>
</Synchronize>
How it works...
As you already know, the Synchronize command runs on the target instance.
However, you cannot process or make changes to the source database while it is
being synchronized. This is implemented through an explicit BEGIN TRANSACTION
command on the source instance. Once all the files are copied over to the target
instance data folder and synchronization is ready to commit its work on the target in-
stance, SSAS issues an explicit ROLLBACK TRANSACTION command on the source
instance to release locks and allow resuming processing.