Good day to all.
I will try to state my question as clearly as possible.
Our organization inherited a SQL Server 2000 database that uses identity fields as the primary key for each of the tables.
We have three servers, that, for the purpose of this question I will name A, B, and C. Data from servers B and C is replicated to server A.
When replication is run, and the data is copied from the publisher servers to the subscriber server, the identity field on each of the corresponding tables on the subscriber server will insert it's own identity field with each added record, which most likely will not match that of the publisher table(s). Since, the identity fields are used as the PK, it seems to us that this may cause problems. The obvious solution would be to create a different primary key. However, we would prefer to first attempt a work around.
Any ideas as to a work around will be greatly appreciated.
Thanks.
I will try to state my question as clearly as possible.
Our organization inherited a SQL Server 2000 database that uses identity fields as the primary key for each of the tables.
We have three servers, that, for the purpose of this question I will name A, B, and C. Data from servers B and C is replicated to server A.
When replication is run, and the data is copied from the publisher servers to the subscriber server, the identity field on each of the corresponding tables on the subscriber server will insert it's own identity field with each added record, which most likely will not match that of the publisher table(s). Since, the identity fields are used as the PK, it seems to us that this may cause problems. The obvious solution would be to create a different primary key. However, we would prefer to first attempt a work around.
Any ideas as to a work around will be greatly appreciated.
Thanks.