October 22, 2002 at 1:41 pm
I am setting up transactional replication in order to provide an up to date backup of a live database.
Using a snapshot to initialise the subscriber does not copy any triggers or identity properties and prime keys are created on the subscriber as unique indexes.
If I use backup/restore instead of snapshot and then create subscription the replication stored procedures (insert, delete and update for each table) are not created and replication fails.
In summary:-
I cannot use snapshot to initialise because the backup database would not be usable by my application.
I cannot use backup/restore because replication does not work.
What is going on? any comments appreciated.
Thanks
October 22, 2002 at 3:37 pm
You dont normally want to create keys on the subscriber - how would you get these back into the publisher without having duplicate keys? Merge handles it by both adding a guid and by using ranges of identity columns. As far as triggers and indexes, you can do that pretty easily (in SQL2K) by running a post snapshot script to make whatever changes you want. If you start from backup anytime after the first snapshot the procs would be there, to do it the first time there is a system proc that will generate the other procs..the name escapes me at the moment, sorry!
Andy
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply