SQL Server Errors

CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

Error Message:Msg 1802, Level 16, State 1, Line 1CREATE DATABASE failed. Some file names listed could not be created. Check related errors. Severity level:16. Description:This error message appears when you try to create a database, but the CREATE DATABASE statement cannot successfully be finished. Consequences:The T-SQL statement can be parsed, but causes the error at […]

Syntax ‘%ls’ is not allowed in schema-bound objects.

Error Message:Msg 1054, Level 15, State 8, Procedure MyOrderView, Line 9Syntax ‘%ls’ is not allowed in schema-bound objects. Severity level:15. Description:This error message appears when you try to use invalid syntax for schema-bound objects. Consequences:The SQL statement cannot be parsed and further execution is stopped. Resolution:Error of the Severity Level 15 are generated by the […]

Constraints of type %ls cannot be created on columns of type %ls.

Error Message:Msg 1760, Level 16, State 0, Line 1Constraints of type %ls cannot be created on columns of type %ls. Severity level:16. Description:This error message appears when you try to create a CHECK constraint for a set of columns with at least one invalid data type for that type of constraint. Consequences:The T-SQL statement can […]

Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses.

Error Message:Msg 497, Level 15, State 1, Line 3Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses. Severity level:15. Description:This error message appears when you try to use a variable in the TABLESAMPLE or REPEATABLE clause. Consequences:The T-SQL statement can be parsed, but causes the error at runtime. Resolution:Error of the Severity Level 15 […]

Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, = or when the subquery is used as an expression.

Error Message:Msg 512, Level 16, State 1, Line 1Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. Severity level:16. Description:This error message appears when you try to use subquery (correlated or not) that returns […]

Cannot insert the value NULL into column ‘%.*ls’, table ‘%.*ls’; column does not allow nulls. %ls fails.

Error Message:Msg 515, Level 16, State 2, Line 9Cannot insert the value NULL into column ‘%.*ls’, table ‘%.*ls’; column does not allow nulls. %ls fails. Severity level:16. Description:This error message appears when you try to insert a NULL marker into a column for which the NOT NULL constrain exists. Consequences:The T-SQL statement can be parsed, […]

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

The TABLESAMPLE clause cannot be used in a view definition or inline table function definition.

Error Message:Msg 478, Level 16, State 0, Procedure MyOrder, Line 5The TABLESAMPLE clause cannot be used in a view definition or inline table function definition. Severity level:16. Description:This error message appears when you try to use the TABLESAMPLE clause inside a view or inline table function. Consequences:The SQL statement cannot be parsed and further execution […]

Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

Error Message:Msg 512, Level 16, State 1, Line 1Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. Severity level:16. Description:This error message appears when you try to use subquery (correlated or not) that returns […]