question

BryanWhitfield-7064 avatar image
0 Votes"
BryanWhitfield-7064 asked AlbertoMorillo edited

Initial Data Sync Incomplete from Hub to Member DBs

Trying out Azure SQL Server hub and member DB sync w/ SQL Server 2019 Express. Hub is Azure SQL Server database. Setup 2 member DB on-prem with 2-way sync. Both member DB were created as 'blank' DBs so sync auto provisioned them. Most of my tables have limited data. My Sales table has the most rows but by no means a substantial amount of data. In both member DBs, then initial sync worked but the Sales data did not sync any rows after 1/31/2021 (even though the hub table has data thru 4/19/2021). What would cause the sync to the local DB to be incomplete?

azure-sql-database
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Deleted everything and started my test again. This time the on-prem Member DB was provisioned and populated with all current data. Next, I setup a new/empty Hub DB on Azure. Configured the sync to be 1-way (Member to Hub). In this test, the Hub DB Sales table only sync'd 3514 rows (again cut off was 1/31/2021). The on-prem Sales table has 19,423 rows. The previous test had the Hub sync to the member DB. So it appear the sync is incomplete regardless if you sync from Hub to Member or Member to Hub.

0 Votes 0 ·

1 Answer

AlbertoMorillo avatar image
0 Votes"
AlbertoMorillo answered AlbertoMorillo edited

Usually the sync process stops on specific dates when one of the following occurs:

  • Schema/datatype incompatibility.

  • Inserting null in non-nullable columns.

  • Violating foreign key constraints.

Please examine in detail the rows related to that day 1/31/2021 and make sure one of the above 3 scenarios is not taking place.

Hope this helps.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.