locked
tracking information in a saperate db at the time of provisioning a for database sync of muliple Sql 2008 db RRS feed

  • Question

  • Hi,

    Is it  possible to provision or re provision a client database for sync and store the tracking information in a different database?

    Is it possible to store the sync related custom stored proc preserved somewhere so that at the time of recreating the scope , it can be directly executed using the script.

    I wanted to keep the sync related data different from the normal db. Even with object and schema prefix, the tracking table and stored proc seems interfering specially when select change SP does not follow the pattern.

    Wednesday, September 5, 2012 9:53 PM

All replies

  • you can script the provisioning and create parts of it on another database.

    you will now have cross database operations though.

    the triggers will be updating tracking tables in a different database. select changes joining tables from two different databases (tracking table and base table). insert/update/stored procedures updating two databases: one for tracking table and the other for the user table.

    not to mention separate security settings, backup, etc that you have to do on both databases.

    imho, not worth all the efforts if your issue is just differentiating sync objects with your other database objects. schema and object prefix is an acceptable way to differentiate the objects already.

    Thursday, September 6, 2012 3:41 AM