Hello,
I have a database with huge amount of master data. This master data should be same at the server and all clients. So I have made a copy of database which contains only the master data and then restores the backup
at Server and the clients. The master database is not provisioned any sync scope.
In future the new master data can be created from server which needs to syncronized to all clients, so I provision the scope without any filters for all the master tables on server and also provisions the same scope on clients too. And then every client
syncronizes with the server. But as the existing master data is already present at all the clients, it first tries to syncronize the data which is already present at the other side too. And the conflict occurs as 'LocalInsertRemoteInsert' for all the master
records. As our database contains huge amout of master data, the initial sync takes much time i.e. more than 2 days :( .
Is there any way to prevent the initial syncronization of the existing records?
Note : In future the existing master data ca be modified at the server, so all the records needs to be populated to _tracking table.
As per JuneT suggession I provisioned the scope on master database and then restored the database at server and the clients. But doing this, no sync happens. I tried to update the existing row which not syncronized even I inserted a record
at server which is also not being syncroniized to cleints :( .
Does anyone have any idea about how to have the sync framework to sync the these type of scopes?
Your help will be highly appreciated.
-Ajinath
Ajinath
