Could not find CHECK constraint for ‘%.*ls’, although the table is flagged as having one.

Product: SQL Server
Event ID: 433
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Could not find CHECK constraint for ‘%.*ls’, although the table is flagged as having one.
This error can occur when the creation of a constraint failed but for some reason the creation was not completely rolled back. It can also be caused by data consistency issue with the system tables in the database where the table listed in the message resides.
User Action

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware related problems.

If you have persistent data inconsistency problems, try to swap out different hardware components to isolate the problem. Check that your system does not have write caching enabled on the disk controller. If you suspect this to be the case, contact your hardware vendor.

Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.


If the problem is not hardware related and a known clean backup is available, restore the database from the backup.


If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

If the error still occurs once there are no errors reported by DBCC CHECKDB, script out the constraints, drop the constraints, and then recreate the constraints. If you still receive the error, transfer the data into a new table and drop the existing table.


Leave a Reply