Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
alk
Starting Member
2 Posts |
 Posted - 2005-05-02 : 10:42:54
|
| I have a table that I'm replicating, and it's a common occurance that a record will be deleted, then right away a new record will be inserted with the same primary key. I know the correct thing to do would be to perform updates, not delete and insert - but I don't have the time to re-write all of the applications that access this table. Will replication be able to handle this task, or will there be a problem because the insert and delete records have identical primary keys ?thanks,Andy |
|
|
mpetanovitch
Yak Posting Veteran
52 Posts |
Posted - 2005-05-02 : 20:18:08
|
| Should not be a problem. Why are you experiencing one??Mike Petanovitch |
 |
|
|
alk
Starting Member
2 Posts |
Posted - 2005-05-03 : 01:21:44
|
| still in the design stage, but I was afriad that the table in the distribution database would be using the same primary key as the publisher, so it would choke when I tried to send an insert and a delete with the same primary key. Another fear is that since the insert and delete would be delivered as part of the same transaction, there might be a problem. I guess it's time to give it a try.thanks |
|
|
|
|
|
|
delete, then insert with same primary key