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:
Create a table with check constraint not for replication:
use pubsgoCREATE TABLE dbo.test5(abc int NOT NULL) ON [PRIMARY]goALTER TABLE dbo.test5 ADD CONSTRAINTCK_test5 CHECK NOT FOR REPLICATION ((abc>0))
Insert a new row:
INSERT INTO pubs..test5 (abc) VALUES (1)
Update the same row:
UPDATE pubs..test5 SET abc=-1 WHERE abc=1
The preceding update should create this error:
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
On the contrary, the preceding update is actually successful.
Do not use the "NOT FOR REPLICATION" option on CHECK CONSTRAINT.
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:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
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:
UPDATE pubs..test5 SET abc=1 WHERE abc=-1
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