Article ID: 246323 - View products that this article applies to.
This article was previously published under Q246323
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56174 (SQLBUG_70)
When a table is created with check constraint and the constraint is set as "NOT FOR REPLICATION", the constraint is not enforced even though the value entered is outside the range of the check constraint. For example:
On the contrary, the preceding update is actually successful.
Server: Msg 547, Level 16, State 1, Line 1
UPDATE statement conflicted with COLUMN CHECK constraint 'CK_test5'. The conflict occurred in database 'pubs', table 'test5', column 'abc'.
The statement has been terminated
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561For more information, contact your primary support provider.
(http://support.microsoft.com/kb/254561/ )INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
Also, when you trying to change the value in the preceding example back to a value that is within the range as in this example:
You may see this error message:
attempt made to perform direct %s to range that is maintained by replication. The conflict occurred in database '%s, table %s, column %s
Contact us for more help