Following Sync 2.0 RTM Conditional Synchronization thread
http://social.microsoft.com/Forums/en-US/syncdevdiscussions/thread/2a274c87-3e9b-433e-b9f0-3a2233df9b2b. I have implemented
http://jtabadero.spaces.live.com/blog/cns!BF49A449953D0591!1187.entry?&_c02_vws=1
approach to synchronize according to the parameters supplied at the synchronization.
I am able to synchronize for all the tables except for 1 table named xxx where, there are only two columns primary key of main table and composite primary key of the table xxx. If i delete records from server and synchronize ,the trace file
is giving details that @P2 parameter for xxx_delete,xxx_selectRow,xxx_InserMetadata is NULL and thus delete changes at server end are not synchronized to client perfectly.
E.g - EmployeeAddressDetails table has two columns employeeId and addressId both of them together form a composite pimary key. In our case only at the server delete case the addressId (@P2) of the xxx_delete,xxx_selectRow,xxx_InserMetadata is sent
as null.
I am not able to get the source of this @P2 = null ( i.e. where it is assigned and how it is sent accros ). I have kept SQL Profiler running to inspect the sync queries but it is not helping.
