Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, June 5, 2019 9:15 PM
1. How long does the data stay in these dss_tracking tables? Is it configurable?
I have not found the doc for this process.
2. The error messages that display in the portal do not show enough detail to diagnose the problem.
Where can I look to get detailed info?
3. How do you reload the data in a table? (Similar to snap a table in replication)
All replies (3)
Wednesday, June 5, 2019 11:05 PM
Hello,
You should not manually manipulate those DSS tracking tables. Please use the deprovision tool to make some cleaning and stop syncing.
On the computer where you installed SQL Agent, under the c:\program files (x86)\Microsoft SQL Azure Data Sync directory you should find an utility named deprovisionUtil.exe. If you run it with the switch /F it will remove the DSS schema and all its objects.
Another option is to use the Sync Agent, select the databases and unregister them. Once unsubscribed, go to your Data Sync in Azure and to the databases node under Sync Groups where appear your participating databases and delete the agent linked to your data sync group (first delete the database reference in this node). When succeeded it is time to delete the data sync group, if failed, there is an option to force delete in the panel with the graphical representation of databases and connections, in the main graphic area. That process allows to clear all data sync synchronization information.
If you want to know why SQL Data Sync is failing, please examine the Event Log (Windows OS) entries on the computer where you installed the SQL Data Sync Agent. Share with us what you find on Event Viewer->Applications and Services Logs->SQL Azure Data Sync Preview or Event Viewer->Applications and Services Logs->Data Sync Service.
Hope this helps.
Regards,
Alberto Morillo
Wednesday, June 5, 2019 11:32 PM
I am syncing Azure DB to Azure DB not using an on prem db.
Thursday, June 6, 2019 4:42 AM
Hello,
Try to delete the sync group, then run the cleanup scripts on the following URL:
https://github.com/vitomaz-msft/DataSyncMetadataCleanup
After that recreate the sync group.
Hope this helps.
Regards,
Alberto Morillo