SQL Server Errors

SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d … %d] of type integer}.

Error Message:Msg 2755, Level 16, State 1, Line 1SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d … %d] of type integer}. Severity level:16. Description:This error message appears when you try to use an invalid option in the SET DEADLOCK_PRIORITY command. Consequences:The T-SQL statement can be parsed, but causes […]

Cannot drop XML Index ‘%.*ls’ using old ‘Table.Index’ syntax, use ‘Index ON Table’ syntax instead.

Error Message:Msg 3749, Level 16, State 1, Line 1Cannot drop XML Index ‘%.*ls’ using old ‘Table.Index’ syntax, use ‘Index ON Table’ syntax instead. Severity level:16. Description:This error message appears when you try to drop a XML index via the DROP INDEX tablename.indexname statement. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. […]

The ROWGUIDCOL property can only be specified on the uniqueidentifier data type.

Error Message:Msg 2761, Level 16, State 2, Line 1The ROWGUIDCOL property can only be specified on the uniqueidentifier data type. Severity level:16. Description:This error message appears when you try to use the ROWGUIDCOL property for a column, which is not of the UNIQUEIDENTIFIER data type. Consequences:The T-SQL statement can be parsed, but causes the error […]

Windowed functions can only appear in the SELECT or ORDER BY clauses.

Error Message:Msg 4108, Level 15, State 1, Line 1Windowed functions can only appear in the SELECT or ORDER BY clauses. Severity level:15. Description:This error message appears when you try to use a windowed function outside a SELECT or ORDER BY clause. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Errors of […]

The SELECT INTO statement cannot have same source and destination tables.

Error Message:Msg 2770, Level 16, State 1, Line 1The SELECT INTO statement cannot have same source and destination tables. Severity level:16. Description:This error message appears when you try to a SELECT INTO statement, but source and destination table of that statement are identical. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. […]

Windowed functions cannot be used in the context of another windowed function or aggregate.

Error Message:Msg 4109, Level 15, State 1, Line 1Windowed functions cannot be used in the context of another windowed function or aggregate. Severity level:15. Description:This error message appears when you try to use a windowed function within another function or aggregate function. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Errors […]

Cannot create procedure ‘%.*ls’ with a group number of %d because a procedure with the same name and a group number of 1 does not currently exist in the database. Must execute CREATE PROCEDURE ‘%.*ls’;1 first.

Error Message:Msg 2730, Level 11, State 1, Procedure ShowMe, Line 5Cannot create procedure ‘%.*ls’ with a group number of %d because a procedure with the same name and a group number of 1 does not currently exist in the database. Must execute CREATE PROCEDURE ‘%.*ls’;1 first. Severity level:11. Description:This error message appears when you try […]

Cannot access temporary tables from within a function.

Error Message:Msg 2772, Level 16, State 1, Procedure MyDate, Line 8Cannot access temporary tables from within a function. Severity level:16. Description:This error message appears when you try to access a temporary table from within a user-defined function. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Errors of the Severity Level 16 […]

The CREATE SCHEMA statement should be followed by a name or authorization keyword.

Error Message:Msg 4111, Level 15, State 1, Line 1The CREATE SCHEMA statement should be followed by a name or authorization keyword. Severity level:15. Description:This error message appears when you try to create a new schema with CREATE SCHEMA without specifying anything else. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Errors […]

Column names in each table must be unique. Column name ‘%.*ls’ in table ‘%.*ls’ is specified more than once.

Error Message:Msg 2705, Level 16, State 3, Line 1Column names in each table must be unique. Column name ‘%.*ls’ in table ‘%.*ls’ is specified more than once. Severity level:16. Description:This error message appears when you try to specify a name for a column more than once upon creation of a table. Consequences:The T-SQL statement can […]