sql server replication: restarting replication after it barfs -- sql server replication

restarting replication after it barfs

chris
8/30/2003 12:41:08 AM

sql server replication: sql2k sp3
I have replication successfully working on a number of tables. Someone tried
to insert a null value where they shouldnt have. I get the message:

Cannot insert the value NULL into column 'cr_username', table
'adv084dk2.dbo.current_run_cr'; column does not allow nulls. INSERT fails.
(Source: sqldev6 (Data source); Error number: 515)

which is fine. But how do I tell SQL to get over it and restart replication.
I keep restarting the Dist agent but then the same message re-appears in a
couple of seconds. How do I kill the bogus insert?

Thanks in advance.
Chris

Re: restarting replication after it barfs

Ron McNulty
8/31/2003 6:06:28 PM

Sounds like the source table allows nulls in that column, else replication
would never have seen the problem.

Removing or modifying the offending source table record should help.

Regards

Ron

[quoted text, click to view]