Re: Merge Replication
From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 01/20/05
- Next message: Pari: "byte by byte level replication versus sql server replication"
- Previous message: Paul Ibison: "Re: Transactions / Commands stuck on distributor. Help!"
- In reply to: mcdojj: "Merge Replication"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 Jan 2005 09:39:33 -0500
Well Microsoft sales will be very happy to sell you a copy of Enterprise
Edition, but it won't solve your problem. You will need to partition your
data so that your identity seeds are different (1 on the publisher and 2 on
the subscriber for example) with an increment of 2.
Either that or extend your PK to include a location specific id, which will
probably involved adding another column to your tables you are replicating.
-- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html "mcdojj" <mcdojj@discussions.microsoft.com> wrote in message news:44E1AA9D-6334-4EEA-A7BB-BC69351E1F6D@microsoft.com... > We are looking into options for bring up a second live business site using > SQL Server 2000 Std edition. The databases will updated at both locations > and need to remain in sync at both locations. Some the tables contain > Identity columns. We have noticed Primary Key issues when we insert into a > new record on different servers and the records are replicated to each other > due to the identity field. Will we need to upgrade to SQL Enterrpise Edition?
- Next message: Pari: "byte by byte level replication versus sql server replication"
- Previous message: Paul Ibison: "Re: Transactions / Commands stuck on distributor. Help!"
- In reply to: mcdojj: "Merge Replication"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
