Answered by:
Sync Framework Locking the table

Question
-
Hello,
I have a centralized SQL server and hundreds of individual instances of SQL Express. I am using MS Sync Framework 2.0 for the synchronization (Download only). When I do the sync using a single user at a time it works well. However if done with multiple users it locks a table (Always a same table!). I am not sure if there is any workaround for this issue.
Please advise.
Monday, September 27, 2010 3:38 PM
Answers
-
Hello JuneT,
Thanks very much for your follow up. Each local database hosts data for all the users. I am not sure what could be the reason. However the sync on this particular talbe hungs for long time and not error message received. After thorough analysis I found that I do not need to sync up this table particularly in my case. On initial load of application it verifies the data in this table and sync them up manually. So I remove this table from my scope list and now I am ready to go..
Thanks again.
- Proposed as answer by Ann Tang [MSFT]Microsoft employee Tuesday, September 28, 2010 6:01 PM
- Marked as answer by Dong CaoMicrosoft employee Friday, October 8, 2010 1:17 AM
Tuesday, September 28, 2010 10:47 AM
All replies
-
can you confirm its locking the table or is it just a case of the multiple users having contention to the same rows?Monday, September 27, 2010 4:07 PM
-
There is separate local database for each user. So the multiple users having contention to the same row is not an issue.Tuesday, September 28, 2010 6:33 AM
-
which table are you seeing being locked? on the client or on the server? am referring to the server. does each user have individual databases on the server as well?Tuesday, September 28, 2010 6:40 AM
-
It is on the client side. There is a single database on server. However the server database used to sync only. There is a separate application to work with server database. We have subset of that application for individual user (each has it own database) and at the end of the day they sync their data to the server database.Tuesday, September 28, 2010 7:24 AM
-
which table is it "locking"?
correct me if am wrong, in your scenario, you have one central database in the server, you have multiple SQL Express instances, each user has their own database. Does each SQL Express host multiple user databases?
sorry but am a bit confused, if each user has its own database, i dont see why running multiple users would result to a lock on a table on one user's database affecting the other user's database when synchronizing.
can you share the specific steps to reproduce the scenario?
any specific error you're getting?
Tuesday, September 28, 2010 7:53 AM -
Hello JuneT,
Thanks very much for your follow up. Each local database hosts data for all the users. I am not sure what could be the reason. However the sync on this particular talbe hungs for long time and not error message received. After thorough analysis I found that I do not need to sync up this table particularly in my case. On initial load of application it verifies the data in this table and sync them up manually. So I remove this table from my scope list and now I am ready to go..
Thanks again.
- Proposed as answer by Ann Tang [MSFT]Microsoft employee Tuesday, September 28, 2010 6:01 PM
- Marked as answer by Dong CaoMicrosoft employee Friday, October 8, 2010 1:17 AM
Tuesday, September 28, 2010 10:47 AM -
if the table has been pre-populated on initial load of the application and you sync it up, chances are you're getting conflicts when downloading and applying the same set of rows thats why its taking long.Tuesday, September 28, 2010 11:01 PM