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 […]

Conversion failed when converting datetime from character string.

Error Message:Msg 241, Level 16, State 1, Line 3Conversion failed when converting datetime from character string. Severity level:16. Description:This error message appears, when SQL Server cannot convert a string to a valid DATETIME value. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the Severity level 16 are generated by […]

Invalid object name ‘%1!’.

Error Message:Msg 208, Level 16, State 1, Line 1Invalid object name ‘%1!’. Severity level:16. Description:This error message appears when you try to reference an object that does not exist in the current database. 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 […]

Arithmetic overflow error for data type %1!, value = %2!.

Error Message:Msg 220, Level 16, State 2, Line 2Arithmetic overflow error for data type %1!, value = %2!. Severity level:16. Description:This error message appears, when the assigment of a value to a variable fails, because the value is larger than the maximum allowed value for the datatype of the variable. Consequences:The T-SQL statement can be […]

%1! is not a valid style number when converting from datetime to a character string.

Error Message:Msg 281, Level 16, State 1, Line 1%1! is not a valid style number when converting from datetime to a character string. Severity level:16. Description:This error message appears when you try to use an invalid style number with the CONVERT() function. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error […]

Divide by zero error encountered.

Error Message:Msg 8134, Level 16, State 1, Line 3Divide by zero error encountered. Severity level:16. Description:This error message appears, when SQL Server encounters a division by 0. 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 […]

Could not find stored procedure ‘%1′.

Error Message:Msg 2812, Level 16, State 62, Line 1Could not find stored procedure ‘%1′. Severity level:16. Description:This error message appears when you try to execute a stored procedure, which does not exist in the specified database. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the Severity level 16 are […]

The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

Error Message:Msg 242, Level 16, State 3, Line 3The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value. Severity level:16. Description:This error message appears, when SQL Server tries to convert a string to a DATETIME value and encounters that the resulting value is outside the valid range […]

Procedure or function %1! has too many arguments specified.

Error Message:Msg 8144, Level 16, State 2, Procedure %1!, Line 0Procedure or function %1! has too many arguments specified. Severity level:16. Description:This error message appears when you try to call a stored procedure and supply more parameters than have been declared for that procedure. Consequences:The T-SQL statement can be parsed, but causes the error at […]

Table ‘%1!” already has a primary key defined on it.

Error Message:Msg 1779, Level 16, State 0, Line 1Table ‘%1!” already has a primary key defined on it. Severity level:16. Description:This error message appears, when you try to create a PRIMARY KEY constraint for a table, for which there is already a PRIMARY KEY declared. Consequences:The T-SQL statement can be parsed, but causes the error […]
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 |