Can someone please advise what would be appropriate method when you want to
implement the merge replication (Kind of a Real time) between different
databases sitting on separate servers.
Is Auto Incremental Field which is PK would be a problem when two users try
to enter records at same time. For example in table#1 user "A" enter some
values at row#3 and got the Id 3,
While at the same time the users "B" in table#2 enter some values at
row#3...would he got Id 3 ? and how it would get replicated.
Do I need to use GUID as PK or some other suggestion?
Shan
Merge replication does not provide real time replication, use automatic
identity range management to avoid the pk conflicts. To do this, drop all
publications where the table you want to bring under automatic identity
range management is publisher. In the publication wizard when you come to
the specify articles dialog box, click on the browse button to the right of
your table name, and select the automatic identity range management tab.
Select a publisher and subscriber range which matches that maximum number of
inserts which might occur between agent syncs, and then make sure your
agents do not run continuously.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Shan" <Shan@.discussions.microsoft.com> wrote in message
news:C97F8918-2523-4064-A6EB-F7C1D7D67BE2@.microsoft.com...
> Can someone please advise what would be appropriate method when you want
to
> implement the merge replication (Kind of a Real time) between different
> databases sitting on separate servers.
> Is Auto Incremental Field which is PK would be a problem when two users
try
> to enter records at same time. For example in table#1 user "A" enter some
> values at row#3 and got the Id 3,
> While at the same time the users "B" in table#2 enter some values at
> row#3...would he got Id 3 ? and how it would get replicated.
> Do I need to use GUID as PK or some other suggestion?
> --
> Shan
Wednesday, March 28, 2012
Merge Replication!
Labels:
advise,
appropriate,
database,
merge,
method,
microsoft,
mysql,
oracle,
real,
replication,
server,
sql,
time,
toimplement
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment