locked
Sync updates from Trigger back to client using SqlServer 2008 change tracking RRS feed

  • General discussion

  • Hi all

    Our development team faces the following difficulty and we are currently unable to find a good solution to it:

    When inserting a new row in the table on the server, we update the row in a after insert trigger to set a identificator field. The problem is that this identificator value is not synced back from the server to the client.

    Cause of the problem is that the client thinks that it already has the correct information for the whole row, since it is the client that initiated the insert of this new row in the server table (and therefore triggered the update of the identificator field after the insert)

    Right now when formulating the problem I think this might be a solution to the problem:

    By declaring in the trigger a different change tracking context with the sqlserver 2008 keywords
    WITH CHANGE_TRACKING_CONTEXT (http://msdn.microsoft.com/en-us/library/bb895330.aspx), 
    the client would no more think the change made by the trigger to be one of his own changes
    and therefore upload the changes made by the trigger.



    • Moved by Tina_Tian Friday, April 22, 2011 7:51 AM (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Thursday, November 20, 2008 8:32 AM