locked
rules for local_create_peer_timestamp when synchronizing other ADO.NET databases RRS feed

  • Question

  • I am working on implementing synchronization with a RMDB that does not support a 64-bit int.  In the examples on the How to: Provision a Server Database for Collaborative Synchronization page, all the local_create_peer_timestamp columns are the @@DBTS, thus unique 64-bit values through out the database which changes on each and every insert and update to the DB.

    What exactly are the rules for the local_create_peer_timestamp values?  From what it appears it must always be increasing.  Must it be unique through out the Per-table metadata or can it simply be unique to one Per-table metadata?  The @@DBTS changes on each and every update or insert, but does the ticker for the local_create_peer_timestamp need to change on updates or just inserts?

    All in all, we have determined that implementing this ticker using a 32-bit value has too high of a risk of roleover for our application if it has to be unique between all the Per-table metadata while updating it on all the inserts and updates through the tables being tracked.

    Thus I am seeking either clerification on the rules which govern this column or some other solution.

    Sam

    Tuesday, September 27, 2011 9:28 PM