SQL Server Errors or Failures Error: 206 to Error: 225
Error: 206, Severity: 16, State: 2, Line: 1
Msg 206, Level 16, State 2, Line 1
Operand type clash: %ls is incompatible with %ls
This error occurs when you try to perform operating between variable or columns whose data types are not compatible for performing such operation.
Example, “Operand type clash: varchar(max) is incompatible with sql_variant” can occur if you try to perform some operation between varchar and sql_varient.
Error: 207, Severity: 16, State: 1, Line: 1
Msg 207, Level 16, State 1, Line 1
Invalid column name ‘%.*ls’.
This error occurs when a column referenced in a Transact-SQL statement was not found in any table specified in the FROM clause of the query. Change the column name to a column name present in one of the tables referenced in the query.
Error: 208, Severity: 16, State: 1, Line: 1
Msg 208, Level 16, State 1, Line 1
Invalid object name ‘%.*ls’.
This error occurs when an object that does not exist is referenced. If the object exists, you might need to include the owner’s name in the object name.
If the object is not owned by the user attempting to access it, and it is not owned by the database owner, all references to the object must include the owner’s name. For example, if user1 creates a table called test, other users must use the name user1.test when they refer to the table.
Error: 209, Severity: 16, State: 1, Line: 1
Msg 209, Level 16, State 1, Line 1
Ambiguous column name ‘%.*ls’.
This error occurs when you are trying to run a select statement that joins multiple tables together that have at least one column with the same name, and then you reference that column without prefixing it with the table.
To resolve this issue specify the table name or table alias and schema name as well
Error: 210, Severity: 16, State: 1, Line 1
Msg 210, Level 16, State 1, Line 1
Conversion failed when converting datetime from binary/varbinary string.
This error message appears when you try to convert an invalid BINARY(VARBINARY) string to a value of type DATETIME. The VARBINARY string must either be valid and convertible to DATETIME.
Error: 211, Severity: 23
Possible schema corruption. Run DBCC CHECKCATALOG.
Error: 212, Severity: 16
Expression result length exceeds the maximum. %d max, %d found.
Error: 213, Severity: 16
Column name or number of supplied values does not match table definition.
Error: 214, Severity: 16
Procedure expects parameter ‘%ls’ of type ‘%ls’.
Error: 215, Severity: 16
Parameters supplied for object ‘%.*ls’ which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.
Error: 216, Severity: 16
Parameters were not supplied for the function ‘%.*ls’.
Error: 217, Severity: 16
Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d).
Error: 218, Severity: 16
Could not find the type ‘%.*ls’. Either it does not exist or you do not have the necessary permission.
Error: 219, Severity: 16
The type ‘%.*ls’ already exists, or you do not have permission to create it.
Error: 220, Severity: 16
Arithmetic overflow error for data type %ls, value = %ld.
Error: 221, Severity: 10
FIPS Warning: Implicit conversion from %ls to %ls.
Error: 222, Severity: 16
The base type “%.*ls” is not a valid base type for the alias data type.
Error: 223, Severity: 11
Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.
Error: 224, Severity: 11
Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.
Error: 225, Severity: 16
The parameters supplied for the %ls “%.*ls” are not valid.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.