SQL Server Errors

Column “%1!.%2!” is invalid in the ORDER BY clause

Error Message:Msg 8127, Level 16, State 1, Line 1Column “%1!.%2!” is invalid in the ORDER BY clause Severity level:16. Description:This error message appears when you try to run an SQL statement, in which you try to sort by a column, that is neither contained in an aggregate function nor in the GROUP BY clause. Consequences:The […]

Cannot add multiple PRIMARY KEY constraints to table ‘%1!’.

Error Message:Msg 8110, Level 16, State 0, Line 1Cannot add multiple PRIMARY KEY constraints to table ‘%1!’. Severity level:16. Description:This error message appears when you try to declare more than one PRIMARY KEY constraint in the same CREATE TABLE statement. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the […]

Invalid column name ‘%.*ls’.

Error Message: Msg 207, Level 16, State 3, Line 1Invalid column name ‘%.*ls’. Severity level: 16. Description:This error message appears when you reference a column in the SELECT list that SQL Server cannot find in any table in the FROM clause. Consequences:The SQL statement cannot be parsed and further execution is stopped. Resolution:Error of the […]

Cannot define PRIMARY KEY constraint on nullable column in table ‘%1!’.

Error Message:Msg 8111, Level 16, State 1, Line 1Cannot define PRIMARY KEY constraint on nullable column in table ‘%1!’. Severity level:16. Description:This error message appears, when you try within a CREATE TABLE statement to create a PRIMARY KEY constraint on a column or a set of columns that allow NULLs. Consequences:The T-SQL statement can be […]

Ambiguous column name ‘%.*ls’.

Error Message: Msg 209, Level 16, State 1, Line 1Ambiguous column name ‘%.*ls’. Severity level: 16. Description:This error message appears when SQL Server is not able to uniquely resolve the column name in the statement. Consequences:The SQL statement cannot be parsed and further execution is stopped. Resolution:Error of the Severity level 16 are generated by […]

Cannot update identity column ‘%1!’.

Error Message:Msg 8102, Level 16, State 1, Line 2Cannot update identity column ‘%1!’. Severity level:16. Description:This error message appears, when you try to UPDATE one or more rows of a column on which the IDENTITY property has been defined Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the Severity […]

A domain error occurred.

Error Message:Msg 3623, Level 16, State 1, Line 1A domain error occurred. Severity level:16. Description:This error message appears, when you to perform an, at least for SQL Server, mathematical illegal operation. 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 […]

There is already an object named ‘%1!’ in the database.

Error Message:Msg 2714, Level 16, State 6, Line 2There is already an object named ‘%1!’ in the database. Severity level:16. Description:This error message appears when you try to create an object wit a name that already exists in the database. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the […]

A TOP N value may not be negative.

Error Message:Msg 127, Level 15, State 1, Line 1A TOP N value may not be negative. Severity level:15. Description:This error message appears when you try to use a negative value in the TOP clause. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the Severity level 15 are generated by […]

The variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure.

Error Message: Server: Msg 134, Level 15, State 1, Line nThe variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure. Severity level: 15. Description:This error message appears when you try to declare a variable that has already been declared. Consequences:The SQL statement cannot 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 |