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 |
|
RogerP
Starting Member
2 Posts |
 Posted - 2008-08-29 : 04:49:45
|
| Hi allWe have a replication set up which works pretty well. Yesterday I did some updates on a history table to adjust the user names to the new naming convention. Unfortunately I forgot that there is a filter defined on that history table which says that only records of the last 30 days should get replicated. Because of those updates I did, the replication wants to apply changes to records which do not exist on the replicat. One solution would be to add those missing records to the target system and let the replication do what it wants to do. But if it's possible I don't want to insert about 5 million records...Is there a way to ignore those errors?Or any other ideas how to solve that?Many thanks in advance!Roger |
|
|
RogerP
Starting Member
2 Posts |
Posted - 2008-08-29 : 09:34:47
|
| Ok, I found the problem and solved it (hopefully)!The primary key of the table is defined as sequence. The procedure that gets called (sp_MSupd_<tablename>) tries to update that field and fails of course.I've altered that procedure and commented the bad line out.CheersRoger |
 |
|
|
|
|
|
Update of non existing data on target database