Cannot bind a default to a computed column or to a column of data type timestamp, varchar(max), nvarchar(max), varbinary(max), xml or sqlclr type.

Error Message:
Msg 15101, Level 16, State 1, Procedure sp_bindefault, Line 158
Cannot bind a default to a computed column or to a column of data type timestamp, varchar(max), nvarchar(max), varbinary(max), xml or sqlclr type.

Severity level:
16.

Description:
This error message appears when you try to bind a via CREATE DEFAULT generated default to a column that has an invalid datatype for a default or is a computed column.

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

Resolution:
Errors of the Severity Level 16 are generated by the user and are corrigible by the user. The statement cannot be executed this way. The column must have a valid datatype.

Versions:
All versions of SQL Server.

Example(s):
USE tempdb;
GO
IF OBJECT_ID(‘tempdb..#t’) > 0
 DROP TABLE #t
GO
IF OBJECT_ID(‘MyDefault’) > 0
 DROP DEFAULT MyDefault;
GO
CREATE TABLE #t
(
 c1 TIMESTAMP NOT NULL
)
GO
CREATE DEFAULT MyDefault AS 42;
Go
EXEC sp_bindefault ‘MyDefault’, ‘#t.c1′;

Remarks:
in the above example we try to bind the default MyDefault to a column of the 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 |