March 19, 2009 at 12:36 am
We need to replicate at least 2 tables. A secondary key in the second table is the primary key in the first table. We need to mark the identity field as (not for replication) so will the right value be created in the primary column of the subscriber if a record is deleted in the first table on the publisher
or
What will happen if I add a record in publisher table delete it immediately and then add a record again. Will the same steps be replicated in the subscriber table when replication is pushed some time later. Otherwise the publisher table identity field and the subscriber table identity field will be off by the increment value.
Thanks
Claude
March 19, 2009 at 10:27 am
The answer is depends on the type of replication used. If it is a replication set up where both the Publisher and subscriber can get updates, then you will have to do something called Identity Range Management. Either you can let Replication itself to take care of it or you can do it manually.
If it is just Snapshot, then you have no problem.
If it is transactional replication, the table will be created in the Subscriber as an Int or a BigInt depending on how you have set up the table.
-Roy
March 23, 2009 at 11:32 pm
Hi Roy,
In our case the data will always be pushed from the Publisher to the Subscriber. Does this mean that we should replicate the identity column on the Publisher ( don't make it not for replication) and on the Subscriber remove the identity column property for the same column.
Thanks very much
Claude
March 24, 2009 at 6:30 am
Set up the replication for publisher with NOT for Replication and create the table in Subscriber as an INT or BIGINT without Identity specefication.
-Roy
March 25, 2009 at 3:08 am
Thanks Roy. Will try it out.
Claude
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply