Cannot bind a default to a column created with or altered to have a default value.

Error Message:
Msg 15103, Level 16, State 1, Procedure sp_bindefault, Line 178
Cannot bind a default to a column created with or altered to have a default value.

Severity level:
16.

Description:
This error message appears when you try to bind a via CREATE DEFAULT generated default to a column that has already a default constraint defined.

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 can be fixed by the SQL Server user. The statement cannot be executed this way. Each column can only have one default value.

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 INT NOT NULL
 CONSTRAINT DF_#t_c1 DEFAULT(0)
)
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 the column c1. Because this column already has a default constraint defined on it, the error is raised.




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 |