Databases Reference
In-Depth Information
Figure 7-17. Selected tables
Open Notepad and copy the contents of the Clipboard, which will reveal that even though the OrganizationLevel
column of the HumanResources.Employee table was not red when defining our dataset, SQL Data Sync cannot sync
that column because “it is either a computed column or is the result of a UNION operator.” Well, indeed that column
is a computed column.
Luckily, this is easy enough to fix. Go back into the Sync Group window, and click the Edit Dataset button.
Select the HumanResources.Employee table and uncheck the OrganizationLevel column. Click the Deploy button
on the toolbar to re-provision all the databases. This time the deployment will succeed and launch the initial
synchronization.
Looking at the Synchronized Data
To validate that the synchronization was successful, jump over to SQL Server Management Studio and open a query
window to the on-premises member database AW2012. Type in the following query:
SELECT * FROM Person.BusinessEntity
Figure 7-18 shows that indeed all rows greater than 10,000 were synchronized to the member databases.
 
Search WWH ::




Custom Search