SQL Server Errors or Failures Error: 354 to Error: 407

SQLServerF1

 

Error: 354, severity: 16,
The target ‘%.*ls’ of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.

Error: 355, severity: 16,
The target table ‘%.*ls’ of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.

Error: 356, severity: 16,
The target table ‘%.*ls’ of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint ‘%ls’.

Error: 357, severity: 16,
The target table ‘%.*ls’ of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule ‘%ls’.

Error: 358, severity: 16,
The target table ‘%.*ls’ of the MERGE statement cannot have any enabled rules. Found rule ‘%ls’.

Error: 359, severity: 16,
The target ‘%.*ls’ of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used.

Error: 360, severity: 16,
The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both.

Error: 361, severity: 16,
The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target

Error: 362, severity: 16,
The query processor could not produce a query plan because the name ‘%.*ls’ in the FORCESEEK hint on table or view ‘%.*ls’ did not match the key column names of the index ‘%.*ls’.

Error: 363, severity: 16,
The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the %S_MSG specified by index ‘%.*ls’.

Error: 364, severity: 16,
The query processor could not produce a query plan because the FORCESEEK hint on view ‘%.*ls’ is used without a NOEXPAND hint. Resubmit the query with the NOEXPAND hint or remove the FORCESEEK hint on the view.

Error: 365, severity: 16,
The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ specified more seek columns than the number of key columns in index ‘%.*ls’.

Error: 366, severity: 16,
The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the column store index ‘%.*ls’.

Error: 401, severity: 16,
Unimplemented statement or expression %ls.

Error: 402, severity: 16,
The data types %s and %s are incompatible in the %s operator.

Error: 403, severity: 16,
Invalid operator for data type. Operator equals %ls, type equals %ls.

Error: 404, severity: 16,
The column reference “inserted.%.*ls” is not allowed because it refers to a base table that is not being modified in this statement.

Error: 405, severity: 16,
A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.

Error: 406, severity: 16,
%ls cannot be used in the PIVOT operator because it is not invariant to NULLs.

Error: 407, severity: 16,
Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x.

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.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *