SQL Server Errors

Cannot insert explicit value for identity column in table ‘%1!’ when IDENTITY_INSERT is set to OFF.

Error Message:Msg 544, Level 16, State 1, Line 1Cannot insert explicit value for identity column in table ‘%1!’ when IDENTITY_INSERT is set to OFF. Severity level:16. Description:This error message appears when you try to insert a value into a column for which the IDENTITY property was declared, but without having set the IDENTITY_INSERT setting for […]

“%1!”: Temporary views are not allowed.

Error Message:Msg 4103, Level 15, State 1, Line 2“%1!”: Temporary views are not allowed. Severity level:15. Description:This error message appears when you try to create a temporary view, analogue to a temporary table. Consequences:The SQL statement cannot be parsed and further execution is stopped. Resolution:Error of the Severity level 15 are generated by the user […]

Database ‘%1!’ already exists.

Error Message:Msg 1801, Level 16, State 3, Line 1Database ‘%1!’ already exists. Severity level:16. Description:This error message appears when you try to create a database with a name under which already a database exists on the specific SQL Server instance. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the […]

Column already has a DEFAULT bound to it.

Error Message:Msg 1781, Level 16, State 1, Line 1Column already has a DEFAULT bound to it. Severity level:16. Description:This error message appears when you try to create a DEFAULTconstraint for a column, for which already a DEFAULT constraint was declared. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the […]

More than one column %1! constraint specified for column ‘%2!’, table ‘t’.

Error Message:Msg 8148, Level 16, State 0, Line 1More than one column %1! constraint specified for column ‘%2!’, table ‘t’. Severity level:16. Description:This error message appears when you try within a CREATE TABLE statement to create more than one constraint for one column for which already another constraint of the same kind was declared in […]

The definition for column ‘%1!’ must include a data type.

Error Message:Msg 173, Level 15, State 1, Line 3The definition for column ‘%1!’ must include a data type. Severity level:15. Description:This error message appears when you try to create a column in a CREATE TABLE statement without specifying a datatype for that column. Consequences:The SQL statement cannot be parsed and further execution is stopped. Resolution:Error […]

The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.

Error Message:Msg 294, Level 16, State 0, Line 1The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error. Severity level:16. Description:This error message appears when you try to convert a string to the SMALLMONEY datatype, but the resulting value is beyond the allowed range for a SMALLMONEY value. Consequences:The […]

Arithmetic overflow error converting expression to data type %1!.

Error Message:Msg 8115, Level 16, State 2, Line 1Arithmetic overflow error converting expression to data type %1!. Severity level:16. Description:This error message appears when you try to convert a value of a certain datatype to another datatype, but that value is too large for the second datatype. Consequences:The T-SQL statement can be parsed, but causes […]

Operand data type %1! is invalid for %2! operator.

Error Message:Msg 8117, Level 16, State 1, Line 1Operand data type %1! is invalid for %2! operator. Severity level:16. Description:This error message appears when the datatype is not allowed for the chosen operator. 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 […]

The conversion of the %1! value %2!’ overflowed an %3! column.

Error Message:Msg 244, Level 16, State 1, Line 1The conversion of the %1! value %2!’ overflowed an %3! column. Severity level:16. Description:This error message appears when you try to convert one INTEGER datatype into another INTEGER datatype, but the value is beyond the allowed range for that second datatype. Consequences:The T-SQL statement can be parsed, […]
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 |