Either column ‘%.*ls.%.*ls’ or referencing column ‘%.*ls.%.*ls’ in foreign key ‘%.*ls’ is a timestamp column. This data type cannot be used with cascading referential integrity constraints.

Error Message:
Msg 1786, Level 16, State 0, Line 1
Either column ‘%.*ls.%.*ls’ or referencing column ‘%.*ls.%.*ls’ in foreign key ‘%.*ls’ is a timestamp column. This data type cannot be used with cascading referential integrity constraints
.

Severity level:
16.

Description:
This error message appears when you try to create a cascading referential integrity operation for a column of the TIMESTAMP data type.

Consequences:
The T-SQL statement can be parsed, but causes the error at runtime.

Resolution:
Error of the Severity Level 16 are generated by the user and can be fixed by the SQL Server user. The statement cannot be executed this way. Cascading referential integrity operations cannot be created for columns of that data type.

Versions:
All versions of SQL Server.

Example(s):
USE tempdb;
GO
IF OBJECT_ID(‘tempdb..t1′) > 0
 DROP TABLE t1
GO
IF OBJECT_ID(‘tempdb..t’) > 0
 DROP TABLE t
GO
CREATE TABLE t
(
 c1 TIMESTAMP PRIMARY KEY
)
GO
CREATE TABLE t1
(
 c1 TIMESTAMP
 CONSTRAINT FK_t_t1_c1 FOREIGN KEY REFERENCES t(c1)
 ON UPDATE CASCADE
)

Remarks:
In the above example we try to create the referential integrity operation ON UPDATE CASCADE for a column of the data type TIMESTAMP. This raises the error.




Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |