I did read here http://msdn.microsoft.com/en-us/library/ms151870.aspx that naming the constraint is recommended. Just wish I knew if that is the cause of the original problem. Thanks for your replies

I don't think the problem would "resolve itself" unless I had manually modified those SPs. Strangely enough "Copy INSERT, UPDATE and DELETE stored procedures" is set to True so...

The article has "Copy check contraints" set to False. This ALTER would certainly add a constraint to default new values to 0. It seems to me that the Log Reader...

Unfortunately I have not made any progress on this issue. As you can see, it has been a quiet thread as well. I will update this thread with any further...

I saw that thread and couldn't confirm that it was the same issue. I'll keep my eyes on it for your response. Thanks Paul.

This is a user database

How did I overlook that?! Thanks for the tip and taking the time to help with something that was so obvious.

Agreed...When read litterally without interpretation or reading more deeply, the question is most correctly answered as "Yes"

Question writer, you cost me two points!! 😉