segunda-feira, 6 de agosto de 2012 14:34
Currently our application uses SQL Merge Replication to sync data from inspections to the sql backend when the user is completed.
From my analysis so far, this is not necessarily a conflict resolving issue, but an merge failure that result
s in a conflict.
2. sync handheld Does not update inspection date (this is the cause)
3. See that the date did not update the database Database Date updated manually using the desktop
4. Sync handheld Generates conflict msg, where the Server DB wins
For some reason, the record on the handheld is not recognized as updated and therefore not synced to the server database. Then it is recognized as updated after it has been updated in the Database and tries to sync back to the handheld, causing the conflict msg.
The Column that is not updated is the Inspection Date. The table has a rowguid and no primary or foreign key.
We are using Filtered publication to cut the amount of data on brought to the mobile device database. We are simply filtering everything on a location guid which should have no impact.
Let me know if additional information is needed.
Todas as Respostas
segunda-feira, 6 de agosto de 2012 14:49ModeradorWhat is the conflict message? It looks like it does sense the change has occured but for some reason is marking it as a conflict.
looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
segunda-feira, 6 de agosto de 2012 16:10Are you using SQL Server Compact? Which build version on device and sync agent? And which server version and SP/CU level. A number of merge replication issues have been fixed in later CU/SP releases, or in later SQL CE builds.
Please mark as answer, if this was it. Visit my SQL Server Compact blog
segunda-feira, 6 de agosto de 2012 18:01
Some of the information i will have to send an email to gather from the clients server.
the information i do have is..
SQL Server Version is 10.0.2531.0. That is SQL 2008 SP1.
The IIS Server is Windows Server 2003 R2 Standard. IIS version is 6.
The .dll is sqlcesa35.dll that we use to sync with the IIS, i believe it is sql compact 3.5? I am unsure how to check that.
It is SQL Server Compact, not sure where to check build version on device or sync agent. (Ill try to look up how to get this information.)
segunda-feira, 6 de agosto de 2012 18:03
There is no conflict message untill AFTER we do the database + mobile change it then it marks a conflict that resolves to the server winning.
The conflict is being resolved properly and the way we want it to handle, its somehow the inspection date is not syncing properly.
sexta-feira, 17 de agosto de 2012 17:51
After poking around im able to see that we use
Sqlserverc in our application using the following
Runtime Version: v2.0.50727
SqlClient in our application is using..