Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
SFx 2.x equivalent of SFx 1.x IncrementalInserts command in the adapter? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am upgrading from SFx 1.x to 2.x.

    In 1.x I was able to modify the Designer-created adapter to append a record to a "subscritption table" each time a new record was sent to a client (so I could keep track of all records that were sent to each client).

    SFx 2.x provisioning creates stored procedures (instead of the Designer's adapter commands).

    Question: Which 2.x stored procedure maps to the 1.x IncrementalInserts command (selectchanges, changerow ...)?

    Alternately, how would be a good way to intercept each insert bound for the client and append a record to a subscription table?

    Wednesday, June 1, 2011 8:14 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Incremental changes are detected using selectchanges sp.

    rather than modifying the selectchanges sp, intercept the changes in the ChangesSelected event of the server provider. you can loop thru the change dataset in there and do whatever you want with the dataset.

    note though that the selected changed row may not necessarily be applied on the client side (there is an error or a conflict), so you're "subscription" table may be out of sync with what was applied. a case of the subscription table recording "what was sent" rather than "what was applied"

    • Marked as answer by P H T Thursday, June 2, 2011 7:41 PM
    Thursday, June 2, 2011 3:26 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Incremental changes are detected using selectchanges sp.

    rather than modifying the selectchanges sp, intercept the changes in the ChangesSelected event of the server provider. you can loop thru the change dataset in there and do whatever you want with the dataset.

    note though that the selected changed row may not necessarily be applied on the client side (there is an error or a conflict), so you're "subscription" table may be out of sync with what was applied. a case of the subscription table recording "what was sent" rather than "what was applied"

    • Marked as answer by P H T Thursday, June 2, 2011 7:41 PM
    Thursday, June 2, 2011 3:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I would say we backup a bit and see what we are trying to achieve here. Are you trying to upgrading the sync application from the DBServerSyncProvider to the SqlSyncProvider ?

    thanks

    Yunwen

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, June 2, 2011 6:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Are you trying to upgrading the sync application from the DBServerSyncProvider to the SqlSyncProvider ?

    Yes
    Thursday, June 2, 2011 7:47 PM