SQL Server Errors

Difference of two datetime columns caused overflow at runtime.

Error Message:Msg 535, Level 16, State 0, Line 1Difference of two datetime columns caused overflow at runtime. Severity level:16. Description:This error message appears when you try to “subtract” two values of the type (SMALL)DATETIME and the resulting value causes an overflow Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of […]

The %ls statement conflicted with the %ls constraint “%.*ls”. The conflict occurred in database “%.*ls”, table “%.*ls”%ls%.*ls%ls.

Error Message:Msg 547, Level 16, State 0, Line 6The %ls statement conflicted with the %ls constraint “%.*ls”. The conflict occurred in database “%.*ls”, table “%.*ls”%ls%.*ls%ls. Severity level:16. Description:This error message appears when you try to perform a DML statement which conflicts with an existing constraint. Consequences:The T-SQL statement can be parsed, but causes the error […]

Must pass parameter number %d and subsequent parameters as ‘@name = value’. After the form ‘@name = value’ has been used, all subsequent parameters must be passed in the form ‘@name = value’.

Error Message:Msg 119, Level 15, State 1, Line 1Must pass parameter number %d and subsequent parameters as ‘@name = value’. After the form ‘@name = value’ has been used, all subsequent parameters must be passed in the form ‘@name = value’. Severity level:15. Description:This error message appears when you try to pass parameters in different […]

Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.

Error Message:Msg 273, Level 16, State 1, Line 1Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column. Severity level:16. Description:This error message appears when insert an explicit value into a column if type TIMESTAMP. Consequences:The T-SQL […]

Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table “%.*ls”. The value or seed must be an integer.

Error Message:Msg 477, Level 15, State 0, Line 1Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table “%.*ls”. The value or seed must be an integer. Severity level:15. Description:This error message appears when you try to use a value of an invalid data type for the ROWS or REPEATABLE option of the […]

The name “%.*s” is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted.

Error Message:Msg 128, Level 15, State 1, Line 5The name “%.*s” is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted. Severity level:15. Description:This error message appears when you try to use an object name in an invalid context. Consequences:The T-SQL statement can […]

The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.

Error Message:Msg 288, Level 16, State 1, Line 3The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only. Severity level:16. Description:This error message appears when you try to non-character values in the string function PATINDEX. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the […]

Table and column names must be supplied for the READTEXT or WRITETEXT utility.

Error Message:Msg 182, Level 15, State 1, Line 5Table and column names must be supplied for the READTEXT or WRITETEXT utility. Severity level:15. Description:This error message appears when for a READTEXT or WRITEXT command either table- or column name is not supplied. Consequences:The SQL statement cannot be parsed and further execution is stopped. Resolution:Error of […]

The xml data type cannot be compared or sorted, except when using the IS NULL operator.

Error Message:Msg 305, Level 16, State 1, Line 2The xml data type cannot be compared or sorted, except when using the IS NULL operator. Severity level:16. Description:This error message appears when you try to group by a column of the data type XML. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. […]

The valid range for MAX_QUEUE_READERS is 0 to 32767.

Error Message:Msg 187, Level 15, State 1, Line 6The valid range for MAX_QUEUE_READERS is 0 to 32767. Severity level:15. Description:This error message appears when you specify an invalid number for the MAX_QUEUE_READER option during a CREATE/ALTER QUEUE statement. Consequences:The SQL statement cannot be parsed and further execution is stopped. Resolution:Error of the Severity level 15 […]