SQL Server Error Messages 10001 to 11000

In this post, we’ll list out the SQL Server Error Messages from the error codes 10001 to 11000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 10001 to 11000

ErrorCodeSeverityErrorMessage
1000116The provider reported an unexpected catastrophic failure.
1000216The provider did not implement the functionality.
1000316The provider ran out of memory.
1000416One or more arguments were reported invalid by the provider.
1000516The provider did not support an interface.
1000616The provider indicated an invalid pointer was used.
1000716The provider indicated an invalid handle was used.
1000816The provider terminated the operation.
1000916The provider did not give any information about the error.
1001016The data necessary to complete this operation was not yet available to the provider.
1001116Access denied.
1002116Execution terminated by the provider because a resource limit was reached.
1002216The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned.
1002316The provider does not support the necessary method.
1002416The provider indicates that the user did not have the permission to perform the operation.
1002516Provider caused a server fault in an external process.
1002616No command text was set.
1002716Command was not prepared.
1002816Authentication failed.
1003216Cannot return multiple result sets (not supported by the provider).
1003316The specified index does not exist or the provider does not support an index scan on this data source.
1003416The specified table or view does not exist or contains errors.
1003516No value was given for one or more of the required parameters.
1004216Cannot set any properties while there is an open rowset.
1005216The insertion was canceled by the provider during notification.
1005316Could not convert the data value due to reasons other than sign mismatch or overflow.
1005416The data value for one or more columns overflowed the type used by the provider.
1005516The data violated the integrity constraints for one or more columns.
1005616The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
1005716Cannot create the row. Would exceed the total number of active rows supported by the rowset.
1005816The consumer cannot insert a new row before releasing previously-retrieved row handles.
1006216The change was canceled by the provider during notification.
1006316Could not convert the data value due to reasons other than sign mismatch or overflow.
1006416The data value for one or more columns overflowed the type used by the provider.
1006516The data violated the integrity constraints for one or more columns.
1006616The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
1006716The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
1006816The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source.
1006916The consumer could not delete the row. The insertion has been transmitted to the data source.
1008116The rowset uses integrated indexes and there is no current index.
1008516RestartPosition on the table was canceled during notification.
1008616The table was built over a live data stream and the position cannot be restarted.
1008716The provider did not release some of the existing rows.
1008816The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed.
1010016Cannot create %S_MSG on view “%.*ls” because it contains the DISTINCT keyword. Consider removing DISTINCT from the view or not indexing the view. Alternatively, consider replacing DISTINCT with GROUP BY or COUNT_BIG(*) to simulate DISTINCT on grouping columns.
1010116Cannot create %S_MSG on view “%.*ls” because it contains the TOP or OFFSET keyword. Consider removing the TOP or OFFSET or not indexing the view.
1010216Cannot create %S_MSG on view “%.*ls” because it contains the TABLESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view.
1010316Cannot create %S_MSG on view “%.*ls” because it uses OPENROWSET, OPENQUERY, or OPENDATASOURCE. Consider not indexing the view, or eliminating OPENQUERY, OPENROWSET, and OPENDATASOURCE.
1010416Cannot create %S_MSG on view “%.*ls” because it references a table using a CONTAINSTABLE or FREETEXTTABLE full-text function. Consider removing use of these functions or not indexing the view.
1010516Cannot create %S_MSG on view “%.*ls” because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view.
1010616Cannot create %S_MSG on view “%.*ls” because it references an internal system rowset provider. Consider not indexing this view.
1010716Cannot create %S_MSG on view “%.*ls” because it uses table variable “%.*ls”. Consider not indexing this view or removing the reference to the table variable.
1010816Cannot create %S_MSG on view “%.*ls” because it references a SQL Server internal table.
1010916Cannot create %S_MSG on view “%.*ls” because it references derived table “%.*ls” (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.
1011016Cannot create %S_MSG on view “%.*ls” because it contains an OUTER APPLY. Consider not indexing the view, or removing OUTER APPLY.
1011116Cannot create %S_MSG on view “%.*ls” because it contains a join using an ODBC standard escape syntax. Consider using an ANSI join syntax instead.
1011216Cannot create %S_MSG on view ‘%.*ls’ because it contains an INNER join that specifies a join hint. Consider removing the join hint.
1011316Cannot create %S_MSG on view “%.*ls” because it uses a LEFT, RIGHT, or FULL OUTER join, and no OUTER joins are allowed in indexed views. Consider using an INNER join instead.
1011416Cannot create %S_MSG on view “%.*ls” because it uses the PIVOT operator. Consider not indexing this view.
1011516Cannot create %S_MSG on view “%.*ls” because it uses the UNPIVOT operator. Consider not indexing this view.
1011616Cannot create %S_MSG on view ‘%.*ls’ because it contains one or more UNION, INTERSECT, or EXCEPT operators. Consider creating a separate indexed view for each query that is an input to the UNION, INTERSECT, or EXCEPT operators of the original view.
1011716Cannot create %S_MSG on view “%.*ls” because the view uses the “*” operator to select columns. Consider referencing columns by name instead.
1011816Cannot create %S_MSG on view “%.*ls” because it contains a GROUP BY ALL. Consider using a GROUP BY instead.
1011916Cannot create %S_MSG on view “%.*ls” because it contains a CUBE, ROLLUP, or GROUPING SETS operator. Consider not indexing this view.
1012116Cannot create %S_MSG on view “%.*ls” because it contains a HAVING clause. Consider removing the HAVING clause.
1012416Cannot create %S_MSG on view “%.*ls” because it references an internal SQL Server column.
1012516Cannot create %S_MSG on view “%.*ls” because it uses aggregate “%.*ls”. Consider eliminating the aggregate, not indexing the view, or using alternate aggregates. For example, for AVG substitute SUM and COUNT_BIG, or for COUNT, substitute COUNT_BIG.
1012616Cannot create %S_MSG on view “%.*ls” because it uses aggregate “%.*ls” with the DISTINCT keyword. Consider not indexing this view or eliminating DISTINCT. Consider use of a GROUP BY or COUNT_BIG(*) view to simulate DISTINCT on grouping columns.
1012716Cannot create %S_MSG on view “%.*ls” because it contains one or more subqueries. Consider changing the view to use only joins instead of subqueries. Alternatively, consider not indexing this view.
1012816Cannot create %S_MSG on view “%.*ls” because it uses a CONTAINS or FREETEXT full-text predicate. Consider eliminating CONTAINS or FREETEXT, or not indexing the view.
1012916Cannot create %S_MSG on view “%.*ls” because it references the inline or multistatement table-valued function “%.*ls”. Consider expanding the function definition by hand in the view definition, or not indexing the view.
1013016Cannot create %S_MSG on view “%.*ls” because it uses non-deterministic common language runtime (CLR) table-valued function “%.*ls”. Consider not indexing the view or changing it to not use this function.
1013116Cannot create %S_MSG on view “%.*ls” because it references imprecise common language runtime (CLR) table-valued function “%.*ls”. Consider not indexing the view.
1013216Cannot create %S_MSG on view “%.*ls” because it references table valued common language runtime (CLR) function “%.*ls”. Consider removing reference to the function or not indexing the view.
1013316Cannot create %S_MSG on view “%.*ls” because function “%.*ls” referenced by the view performs user or system data access.
1013416Cannot create %S_MSG on view “%.*ls” because it contains more than one APPLY. Consider not indexing the view, or using only one APPLY.
1013616Cannot create %S_MSG on view “%.*ls” because it uses the aggregate COUNT. Use COUNT_BIG instead.
1013716Cannot create %S_MSG on view “%.*ls” because it references common table expression “%.*ls”. Views referencing common table expressions cannot be indexed. Consider not indexing the view, or removing the common table expression from the view definition.
1013816Cannot create %S_MSG on view ‘%.*ls’ because its select list does not include a proper use of COUNT_BIG. Consider adding COUNT_BIG(*) to select list.
1013916Cannot create %S_MSG on view ‘%.*ls’ because the view uses an implicit conversion from string to datetime or smalldatetime. Use an explicit CONVERT with a deterministic style value.
1014016Cannot create %S_MSG on view ‘%.*ls’ because the view contains a table hint. Consider removing the hint.
1014116Cannot create %S_MSG on view ‘%.*ls’ because it references CLR routine (function or method) ‘%.*ls’ outside non-key columns of SELECT list. Recreate or alter view so it does not reference CLR routines except in non-key columns of SELECT list, and then create index.
1014216Cannot create %S_MSG on view “%.*ls” because it contains an APPLY. Consider not indexing the view, or removing APPLY.
1014316Cannot create %S_MSG on view “%.*ls” because it contains a ranking or aggregate window function. Remove the function from the view definition or, alternatively, do not index the view.
1014416Cannot create %S_MSG on view ‘%.*ls’ because it uses the CHANGETABLE function.
1014516Cannot create %S_MSG on the view ‘%.*ls’ because it references a sparse column set. Views that contain a sparse column set cannot be indexed. Consider removing the sparse column set from the view or not indexing the view.
1014616Cannot create %S_MSG on the view ‘%.*ls’ because it uses the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function.
1014716Cannot create %S_MSG on the view ‘%.*ls’ because it uses temporal FOR SYSTEM_TIME clause.
1014816Cannot create %S_MSG on the view ‘%.*ls’ because it uses OPENJSON.
1014916Index that has SNAPSHOT_MATERIALIZATION cannot be created on view ‘%.*ls’ because view definition contains memory-optimized table(s).
1015016Cannot create %S_MSG on the view ‘%.*ls’ because it references a scalar UDF that is inlineable.
1021116Cannot invoke mutator on a null CLR type value.
1022716Field “%.*ls” of type “%.*ls.%.*ls” cannot be updated because the field is “%.*ls”.
1024016Could not find UdtExtensions.dll. Please check your installation.
1030016Assembly ‘%.*ls’ references assembly ‘%.*ls’, which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %S_MSG). Please load the referenced assembly into the current database and retry your request.
1030116Assembly ‘%.*ls’ references assembly ‘%.*ls’, which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %s). Please load the referenced assembly into the current database and retry your request.
1030216Could not get path for SQL Server: ‘%ls’.
1030316Could not create AppDomain manager: ‘%.*ls’.
1030416Failed to enter Common Language Runtime (CLR) with HRESULT 0x%x. This may due to low resource conditions.
1030516The Init method for a CLR table-valued function must be annotated with SqlFunctionAttribute.
1030616The SqlFunctionAttribute of the Init method for a CLR table-valued function must set the FillRowMethodName property.
1030716The FillRowMethodName property of SqlFunctionAttribute does not contain a valid method name.
1030810Warning: The Microsoft .NET Framework assembly ‘%.*ls’ you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
1030910Warning: The SQL Server client assembly ‘%.*ls’ you are registering is not fully tested in SQL Server hosted environment.
1031010AppDomain %i (%.*ls) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
1031110AppDomain %i (%.*ls) is marked for unload due to memory pressure.
1031216.NET Framework execution was aborted. The UDP/UDF/CLR type did not revert thread token.
1031316An error occurred while using the .NET Framework during %S_MSG. The server may be running out of resources. Try running the query again. If the problem persist, contact a support professional. %.*ls
1031416An error occurred in the Microsoft .NET Framework while trying to load assembly id %d. The server may be running out of resources, or the assembly may not be trusted. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: %.*ls
1031616The app domain with specified version id (%d) was unloaded due to memory pressure and could not be found.
1031716An error occurred trying to get file version info for the file ‘%s’.
1031816‘%.*ls’ failed because parameter %d of method ‘%.*ls’ of type ‘%.*ls’ is annotated with unsupported attribute System.ParamArrayAttribute.
1031916UserDefinedType method call failed because parameter %d of method ‘%.*ls’ of type ‘%.*ls’ is annotated with unsupported attribute System.ParamArrayAttribute.
1032016Method name ‘%.*ls’ is invalid for ‘%.*ls’.
1032116Method name ‘%.*ls’ is invalid for UserDefinedType method call.
1032216Type %.*ls not found in database %.*ls
1032316Invalid user code has been identified by .Net Framework Managed Debug Assistant %.*ls
1032416WITH ENCRYPTION option of CREATE TRIGGER is only applicable to T-SQL triggers and not to CLR triggers.
1032516The server is shutting down due to stack overflow in user’s unmanaged code.
1032616Two versions of assembly ‘%.*ls’ cannot coexist in database ‘%.*ls’. Keep one version and drop the other.
1032714%ls ASSEMBLY for assembly ‘%.*ls’ failed because assembly ‘%.*ls’ is not trusted. The assembly is trusted when either of the following is true: the assembly is signed with a certificate or an asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission, or the assembly is trusted using sp_add_trusted_assembly.
1032816There is not enough stack to create appdomain ‘%.*ls’.
1032916.Net Framework execution was aborted. %.*ls
1033016ALTER ASSEMBLY failed because serialization layout of type ‘%s’ would change as a result of a change in type ‘%s’ in the updated assembly. Persisted types are not allowed to change serialization layout.
1033116Type ‘%ls’ in assembly ‘%.*ls’ derives from a generic type which is not supported for a CLR Type.
1033216Assembly “%.*ls” was built using version %.*ls of the .NET Framework. SQL Server currently uses version %s.
1033316Failed to obtain ICLRAppDomainResourceMonitor interface from CLR. The error code from CLR was: 0x%x. As a result, resource monitoring won’t work for AppDomain with ID %d.
1033416Changing the database compatibility level has caused data to be marked as unchecked in one or more objects in database %s. Refer to the column has_unchecked_assembly_data in the sys.tables and sys.views to locate all such objects.
1033516The Common Language Runtime (CLR) was loaded in an unsupported manner. This can occur if an extended stored procedure or OLE Automation object running in SQL Server calls into managed code before the CLR integration runtime host loads the CLR. You need to restart SQL Server to use CLR integration features.
1033610Failed to enque task to start CLR during SQL server startup. Error code: %u. CLR will be started in an on-demand fashion.
1033716An internal error occurred.
1033816Verification of assembly failed. Could not open the physical file ‘%.*ls’: %ls.
1033916Verification of assembly failed. Could not read from the physical file “%.*ls”: %ls.
1034016DROP ASSEMBLY failed. Error code: 0x%x.
1034116Assembly ‘%.*ls’ cannot be loaded because Azure SQL Database does not support user-defined assemblies. Contact Azure Technical Support if you have questions.
1034216Assembly ‘%.*ls’ cannot be loaded because this edition of SQL Server only supports SAFE assemblies.
1034314CREATE or ALTER ASSEMBLY for assembly ‘%.*ls’ with the SAFE or EXTERNAL_ACCESS option failed because the ‘clr strict security’ option of sp_configure is set to 1. Microsoft recommends that you sign the assembly with a certificate or asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission. Alternatively, you can trust the assembly using sp_add_trusted_assembly.
1034416Internal table access error: failed to access the Trusted Assemblies internal table with HRESULT: 0x%x. Contact Customer Support Services.
1034516The assembly hash ‘0x%.*ls’ is already trusted.
1034616The assembly hash ‘0x%.*ls’ is not currently trusted. No action was taken.
1034716Common Language Runtime(CLR) is not enabled on this instance.
1050116Cannot create plan guide ‘%.*ls’ because type ‘%.*ls’ provided is not allowed.
1050216Cannot create plan guide ‘%.*ls’ because the statement specified by @stmt and @module_or_batch, or by @plan_handle and @statement_start_offset, matches the existing plan guide ‘%.*ls’ in the database. Drop the existing plan guide before creating the new plan guide.
1050316Operation ‘%.*ls’ is not allowed.
1050416Cannot create plan guide ‘%.*ls’ because parameter @hints is incorrect. Use N’OPTION ( <query_hint> [ ,…n ] )’.
1050516Cannot create plan guide ‘%.*ls’ because value ‘%.*ls’ provided for @module_or_batch is not legal two-part name. Use ‘schema_name.object_name’.
1050616Cannot create plan guide ‘%.*ls’ because parameter @stmt has more than one statement.
1050716Cannot create plan guide ‘%.*ls’ because the statement specified by @stmt and @module_or_batch, or by @plan_handle and @statement_start_offset, does not match any statement in the specified module or batch. Modify the values to match a statement in the module or batch.
1050816Cannot ‘%ls’ plan guide ‘%.*ls’ because it does not exist or you do not have permission. Verify plan guide name and database of current session, and that you have needed permission.
1050916Cannot create plan guide ‘%.*ls’ because the statement specified by @stmt or @statement_start_offset either contains a syntax error or is ineligible for use in a plan guide. Provide a single valid Transact-SQL statement or a valid starting position of the statement within the batch. To obtain a valid starting position, query the ‘statement_start_offset’ column in the sys.dm_exec_query_stats dynamic management function.
1051016Cannot create plan guide ‘%.*ls’ because there is already a plan guide with that name in the database. Use a unique name.
1051216Cannot create plan guide ‘%.*ls’ because object ‘@module_or_batch’ is encrypted. Consider tuning query using other techniques such as indexes and statistics.
1051316Cannot %S_MSG %S_MSG ‘%.*ls’ because it is referenced by plan guide ‘%.*ls’. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.
1051516Cannot create plan guide ‘%.*ls’ because the module ‘%.*ls’ does not exist or you do not have needed permission.
1051616Cannot create plan guide ‘%.*ls’ because @module_or_batch can not be compiled.
1051716Cannot create plan guide ‘%.*ls’ because you do not have needed permission. Alter database permission required.
1051816Cannot execute sp_control_plan_guide because of insufficient permissions to control plan guide ‘%.*ls’. Alter permission on object referenced by plan guide, or alter database permission required.
1051916Cannot create plan guide ‘%.*ls’ because the hints specified in @hints cannot be applied to the statement specified by either @stmt or @statement_start_offset. Verify that the hints can be applied to the statement.
1052016Cannot create plan guide ‘%.*ls’ because @type was specified as ‘%ls’ and a non-NULL value is specified for the parameter ‘%ls’. This type requires a NULL value for the parameter. Specify NULL for the parameter, or change the type to one that allows a non-NULL value for the parameter.
1052116Cannot create plan guide ‘%.*ls’ because @type was specified as ‘%ls’ and the parameter ‘%ls’ is NULL. This type requires a non-NULL value for the parameter. Specify a non-NULL value for the parameter, or change the type to one that allows a NULL value for the parameter.
1052216Cannot create plan guide ‘%.*ls’ because @hints has illegal value. @hints must be OPTION(PARAMETERIZATION FORCED) or OPTION(PARAMETERIZATION SIMPLE) if @type is ‘template’.
1052316Cannot generate query template because @querytext does not contain a valid single query.
1052416Cannot parameterize @querytext.
1052510Plan guide ‘%.*ls’ matched statement after it was parameterized automatically by FORCED or SIMPLE parameterization, but the RECOMPILE hint it contains was ignored. RECOMPILE is not supported on automatically parameterized statements. Consider dropping this plan guide or removing RECOMPILE from it.
1052616Cannot drop %S_MSG ‘%.*ls’ because its trigger ‘%.*ls’ is referenced by plan guide ‘%.*ls’. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.
1052716Cannot create plan guide ‘%.*ls’ because the object ‘%.*ls’ is a temporary object.
1052816Cannot create plan guide ‘%.*ls’ because its name is invalid. Plan guide name cannot begin with a ‘#’ character.
1052916Cannot create plan guide ‘%.*ls’ because there is already a planguide ‘%.*ls’ of @type ‘template’ on @stmt.
1053016Cannot create plan guide ‘%.*ls’ because the statement specified by @statement_start_offset does not match any statement in specified module or batch. Consider modifying @statement_start_offset to match a statement in module or batch.
1053116Cannot create plan guide ‘%.*ls’ from cache because the user does not have adequate permissions. Grant the VIEW SERVER STATE permission to the user creating the plan guide.
1053216Cannot create plan guide ‘%.*ls’ because the batch or module specified by @plan_handle does not contain a statement that is eligible for a plan guide.  Specify a different value for @plan_handle.
1053316Cannot create plan guide ‘%.*ls’ because the plan guide name exceeds 124, the maximum number of characters allowed. Specify a name that contains fewer than 125 characters.
1053416Cannot create plan guide ‘%.*ls’ because the value specified for @params is invalid. Specify the value in the form <parameter_name> <parameter_type>, or specify NULL.
1053516Cannot create plan guide ‘%.*ls’ because a plan was not found in the plan cache that corresponds to the specified plan handle. Specify a cached plan handle. For a list of cached plan handles, query the sys.dm_exec_query_stats dynamic management view.
1053616Cannot create plan guide ‘%.*ls’ because the batch or module corresponding to the specified @plan_handle contains more than 1000 eligible statements. Create a plan guide for each statement in the batch or module by specifying a statement_start_offset value for each statement.
1053716Cannot enable plan guide ‘%.*ls’ because the enabled plan guide ‘%.*ls’ contains the same scope and starting offset value of the statement. Disable the existing plan guide before enabling the specified plan guide.
1053816Cannot find the plan guide either because the specified plan guide ID is NULL or invalid, or you do not have permission on the object referenced by the plan guide. Verify that the plan guide ID is valid, the current session is set to the correct database context, and you have ALTER permission on the object referenced by the plan guide or ALTER DATABASE permission.
1053916Cannot create plan guide ‘%.*ls’ from cache because a query plan is not available for the statement with start offset %d.This problem can occur if the statement depends on database objects that have not yet been created. Make sure that all necessary database objects exist, and execute the statement before creating the plan guide.
1060116Cannot specify included columns for a clustered index.
1060216Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement is not allowed.
1060316Cannot rebuild clustered index ‘%.*ls’ on view ‘%.*ls’ because the view is dependent on base table ‘%.*ls’ whose clustered index ‘%.*ls’ is disabled.
1060416Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified.
1060516Cannot disable primary key index “%.*ls” on table “%.*ls” because the table is published for replication.
1060616Cannot disable the clustered index “%.*ls” on view “%.*ls” because the indexed view is published for replication.
1060716The clustered index ‘%.*ls’ on table ‘%.*ls’ cannot be disabled because the table has change tracking enabled. Disable change tracking on the table before disabling the clustered index.
1060816The index ‘%.*ls’ on table ‘%.*ls’ cannot be disabled because the table has change tracking enabled. Change tracking requires a primary key constraint on the table, and disabling the index will drop the constraint. Disable change tracking on the table before disabling the index.
1060916Filtered %S_MSG ‘%.*ls’ cannot be created on table ‘%.*ls’ because the column ‘%.*ls’ in the filter expression is a computed column. Rewrite the filter expression so that it does not include this column.
1061016Filtered index ‘%.*ls’ cannot be created on object ‘%.*ls’ because it is not a user table. Filtered indexes are only supported on tables. If you are trying to create a filtered index on a view, consider creating an indexed view with the filter expression incorporated in the view definition.
1061116Filtered %S_MSG ‘%.*ls’ cannot be created on table ‘%.*ls’ because the column ‘%.*ls’ in the filter expression is compared with a constant of higher data type precedence or of a different collation. Converting a column to the data type of a constant is not supported for filtered %S_MSG. To resolve this error, explicitly convert the constant to the same data type and collation as the column ‘%.*ls’.
1061216Filtered %S_MSG ‘%.*ls’ cannot be created on table ‘%.*ls’ because the column ‘%.*ls’ in the filter expression is compared with a constant that cannot be converted to the data type of the column. Rewrite the filter expression so that it does not include this comparison.
1061716Index ‘%.*ls’ could not be created or rebuilt. The key length for this index (%d bytes) exceeds the maximum allowed length of ‘%d’ bytes when using the vardecimal storage format.
1061816Cannot %S_MSG filtered index ‘%.*ls’ on table ‘%.*ls’ because the statement sets the IGNORE_DUP_KEY option to ON. Rewrite the statement so that it does not use the IGNORE_DUP_KEY option.
1061916Filtered %S_MSG ‘%.*ls’ cannot be created on table ‘%.*ls’ because the column ‘%.*ls’ in the filter expression is of a CLR data type. Rewrite the filter expression so that it does not include this column.
1062016Filtered %S_MSG ‘%.*ls’ cannot be created on table ‘%.*ls’ because the filter expression contains a comparison with a literal NULL value. Rewrite the comparison to use the IS [NOT] NULL comparison operator to test for NULL values.
1062116The index ‘%.*ls’ on table ‘%.*ls’ could not be created because the column ‘%.*ls’ in the filter expression of the index is a column set.
1062216The %S_MSG ‘%.*ls’ could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns or a column set column.
1062316Filtered statistics ‘%.*ls’ cannot be created on object ‘%.*ls’ because it is not a user table. Filtered statistics are only supported on user tables.
1062916The data type specified for column ‘%.*ls’ in table ‘%.*ls’ cannot be used as a column in the distribution key of an index.
1063116Index ‘%.*ls’ could not be created or rebuilt. A unique or clustered index on a federated table must contain the federated column.
1063216Index ‘%.*ls’ could not be created. Views cannot be indexed in a federated database.
1063316Invalid online index creation operation
1063410An ‘%.*ls’ statement was executed on object ‘%.*ls’ by hostname ‘%.*ls’, host process ID %d using the WAIT_AT_LOW_PRIORITY options with MAX_DURATION = %d and ABORT_AFTER_WAIT = BLOCKERS. Blocking user sessions will be killed after the max duration of waiting time.
1063516An online operation cannot be performed for ‘%.*ls’ because the index contains column of large object type, and in the same transaction there are update operations before this online operation. Put the online operation outside the transaction or put it before any updates in the transaction.
1063616Ignore in Optimization cannot be set for ‘%.*ls’ on ‘%.*ls.%.*ls’ because it is only applicable to non-clustered B-tree or columnstore indexes.
1063716Cannot perform this operation on ‘%.*ls’ with ID %I64d as one or more indexes are currently in resumable index rebuild state. Please refer to sys.index_resumable_operations for more details.
1063816ALTER INDEX ‘%S_MSG’ failed. There is no pending resumable index operation for the index ‘%.*ls’ on ‘%.*ls’.
1063916Resumable index operation for %S_MSG ‘%.*ls’ failed because the index contains column ‘%.*ls’ of type timestamp as a key column.
1064016Ignore in Optimization cannot be set for an index on ‘%.*ls.%.*ls’ because it is only applicable to indexes on user defined disk-based tables.
1064116ALTER INDEX PAUSE failed. There is no actively running resumable index operation for the index ‘%.*ls’ on ‘%.*ls’.
1064216SNAPSHOT_MATERIALIZATION cannot be set for index ‘%.*ls’ on ‘%.*ls’ because it is only applicable to indexes on views.
1064316SNAPSHOT_MATERIALIZATION cannot be set for ‘%.*ls’ on ‘%.*ls’ because it is only applicable to clustered indexes on views.
1064416Resumable index operation for %S_MSG ‘%.*ls’ failed because the index contains the computed column ‘%.*ls’ as a key or partitioning column. If this is a non clustered index, the column will be implicitly included as a key column if it is part of the clustered index key.
1064510Warning: An existing resumable operation with the same options was identified for the same index on ‘%.*ls’. The existing operation will be resumed instead.
1064616Index ‘%.*ls’ on view ‘%.*ls’ that has SNAPSHOT_MATERIALIZATION cannot be dropped using the DROP_EXISTING option.
1064716Index ‘%.*ls’ on ‘%.*ls’ that has SNAPSHOT_MATERIALIZATION cannot be altered.
1064816SNAPSHOT_MATERIALIZATION cannot be set for partitioned index ‘%.*ls’ on ‘%.*ls’.
1064916Nonclustered index ‘%.*ls’ cannot be created on ‘%.*ls’ that has clustered index ‘%.*ls’ with SNAPSHOT_MATERIALIZATION.
1065016Refresh of snapshot view(s) requires snapshot isolation to be enabled on the database.
1065116Refresh of snapshot view failed because view ‘%.*ls.%.*ls’ does not exist.
1065216Refresh of snapshot view failed because ‘%.*ls.%.*ls’ is not a snapshot view.
1065316Refresh of snapshot view failed.
1065416Refresh of snapshot view failed because lock could not be obtained on the database.
1065516Refresh of snapshot view failed because view is not specified in two-part name format.
1065610The resumable index operation for index ‘%.*ls’ on object ‘%.*ls’ was paused.
1065710The resumable index ‘%.*ls’ on object ‘%.*ls’ has been paused for ‘%.2f’ hours.
1065816Stored procedure ‘%ls’ is currently disabled.
1065910An ALTER INDEX ‘%S_MSG’ was executed for index ‘%.*ls’ on object ‘%.*ls’ by hostname ‘%.*ls’.
1066013The online index build operation was chosen as a deadlock victim over 500 times while attempting to process a single row. Resolve the blocking concurrent operation, and rerun the query.
1066110The refresh operation for all snapshot views failed because there was another refresh operation (either for all or a single snapshot view) in progress.
1066210The refresh operation for snapshot view ‘%.*ls’ failed because another refresh operation for the same snapshot view was already in progress.
1066310The refresh operation for snapshot view ‘%.*ls’ failed because refresh operation for all snapshot views was already in progress.
1066416Cannot specify included columns for indexes on memory optimized tables.
1066515‘%.*ls’ with DROP_EXISTING option is not supported with %S_MSG option.
1066616Cannot resume index build as required DOP %d (DOP operation was started with) is not available. Please ensure sufficient DOP is available or abort existing index operation and try again.
1066710Warning: Create Index was started with MAXDOP %d. The operation will resume with MAXDOP value %d.
1066816The %S_MSG option is not supported for creating an index on a heap.
1066916The %S_MSG option is not supported for creating a nonclustered index on clustered columnstore index.
1067016Resumable index creation for %S_MSG ‘%.*ls’ failed because the index includes a large object column ‘%.*ls’.
1067116The %S_MSG option is not supported for creating a filtered index.
1067216The %S_MSG option is not supported for creating a clustered index on a relation that has a filtered index.
1067316Cannot resume index creation due to incorrect persisted state found. Please ABORT the operation and try again.
1067416The %S_MSG option is not supported for creating a clustered index on a table containing nonclustered columnstore index.
1070016The table-valued parameter “%.*ls” is READONLY and cannot be modified.
1070115The READONLY option cannot be used in an EXECUTE or CREATE AGGREGATE statement.
1070215The WITH CUBE and WITH ROLLUP options are not permitted with a ROLLUP, CUBE, or GROUPING SETS specification.
1070315Too many grouping sets. The maximum number is %d.
1070415To rethrow an error, a THROW statement must be used inside a CATCH block. Insert the THROW statement inside a CATCH block, or add error parameters to the THROW statement.
1070515Subqueries are not allowed in the OUTPUT clause.
1070615Too many expressions are specified in the GROUP BY clause. The maximum number is %d when grouping sets are supplied.
1070715The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode.  They are only allowed in 100 mode or higher.
1070815DEFAULT is not allowed on the right hand side of “%.*ls”
1070915The number of columns for each row in a table value constructor must be the same.
1071015An action of type ‘%S_MSG’ is not allowed in the ‘WHEN NOT MATCHED’ clause of a MERGE statement.
1071115An action of type ‘INSERT’ is not allowed in the ‘%S_MSG’ clause of a MERGE statement.
1071215The pseudocolumn ‘%.*ls’ cannot be part of an index or used as partitioning column.
1071315A MERGE statement must be terminated by a semi-colon (;).
1071415An action of type ‘%S_MSG’ cannot appear more than once in a ‘%S_MSG’ clause of a MERGE statement.
1071515‘%.*ls’ is not a valid hint.
1071615A nested INSERT, UPDATE, DELETE, or MERGE statement must have an OUTPUT clause.
1071715The %S_MSG clause is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
1071815Query hints are not allowed in nested INSERT, UPDATE, DELETE, or MERGE statements.
1071916Foreign key relationships from a memory optimized table with DURABILITY set to SCHEMA_AND_DATA to a memory optimized table with DURABILITY set to SCHEMA_ONLY are not supported.
1072015An OUTPUT INTO clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
1072115The WHERE CURRENT OF clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
1072215The DISTINCT keyword is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
1072315In a MERGE statement, a variable cannot be set to a column and expression in the same assignment in the SET clause of an UPDATE action. Assignments of the form ‘SET @variable = column = expression’ are not valid in the SET clause of an UPDATE action in a MERGE statement. Modify the SET clause to only specify assignments of the form ‘SET @variable = column’ or ‘SET @variable = expression’.
1072415The FORCESEEK hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
1072515Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
1072615User defined aggregates do not support default parameters.
1072715A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a JOIN or APPLY operator.
1072815A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed as the table source of a PIVOT or UNPIVOT operator.
1072915A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in a SELECT statement that is not the immediate source of rows for an INSERT statement.
1073015A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement.
1073115A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE statement.
1073215A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator.
1073315A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the USING clause of a MERGE statement.
1073416Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator.
1073515Incorrect WHERE clause for filtered %S_MSG ‘%.*ls’ on table ‘%.*ls’.
1073615A full-text stoplist statement must be terminated by a semi-colon (;).
1073715In an ALTER TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL must be specified. The PARTITION=ALL clause is used to reinforce that all partitions of the table or index will be rebuilt, even if only a subset is specified in the DATA_COMPRESSION clause.
1073815The number of row value expressions in the INSERT statement exceeds the maximum allowed number of %d row values.
1073915The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead.
1074015A search property list statement must end with a semicolon (;).
1074115A TOP can not be used in the same query or sub-query as a OFFSET.
1074215The offset specified in a OFFSET clause may not be negative.
1074315The number of rows provided for a OFFSET clause must be an integer.
1074415The number of rows provided for a FETCH clause must be greater then zero.
1074515The FORCESCAN hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
1074615The FORCESCAN hint is specified simultaneously with the FORCESEEK hint. Remove one of the hints and resubmit the query.
1074715The parameterized FORCESEEK hint cannot be simultaneously used with INDEX hints or a non-parameterized FORCESEEK hint on the same object. Use either INDEX hints and a non-parameterized FORCESEEK hint or use a parameterized FORCESEEK hint without INDEX hints for each table or view.
1074815There are multiple FORCESEEK hints specified on the same table or view. Remove the extra FORCESEEK hints and resubmit the query.
1074915The FORCESEEK hint cannot be used with index 0. Correct the index provided to the FORCESEEK hint and resubmit the query.
1075015The FORCESCAN hint cannot be used with more than one INDEX hint. Remove the extra INDEX hints and resubmit the query.
1075115The ORDER BY in WITHIN GROUP clause of ‘%.*ls’ function must have exactly one expression.
1075215The function ‘%.*ls’ may not have a window frame.
1075315The function ‘%.*ls’ must have an OVER clause.
1075415The function ‘%.*ls’ must have a WITHIN GROUP clause.
1075515The function ‘%.*ls’ takes between %d and %d arguments.
1075615Window frame with ROWS or RANGE must have an ORDER BY clause.
1075715The function ‘%.*ls’ may not have a WITHIN GROUP clause.
1075815The function ‘%.*ls’ may not have ORDER BY in OVER clause.
1075915Use of DISTINCT is not allowed with the OVER clause.
1076016Scale argument is not valid. Valid expressions for data type %ls scale argument are integer constants and integer constant expressions.
1076116Invalid data type %.*ls in function %.*ls.
1076216The %.*ls function is not allowed in the current compatibility mode.  It is only allowed in 110 mode or higher.
1076315GROUP BY clause can only contain one query hint. Remove the extra hints and re-run the query.
1076415Number of grouping columns in the query exceeded maximum number allowed. SQL Server allows 64k grouping columns. Reduce number of grouping columns and re-run the query.
1076515DISTRIBUTED_AGG and CENTRAL_AGG hints cannot be used with a CUBE or ROLLUP clause. Modify the query and re-run it.
1076615CENTRAL_AGG must be specified after all columns in the GROUP BY clause. Modify the query and re-run it.
1076715DISTRIBUTED_AGG hint cannot be used when the GROUP BY clause contains the same column more than once. Modify the query and re-run it.
1076815LABEL hint can only be used one time in the query. Modify the query and re-run it.
1076915SET options are not supported inside ATOMIC blocks.
1077015The SERVER option and one of CREDENTIAL or FEDERATED_SERVICE_ACCOUNT = ON options are required for setting REMOTE_DATA_ARCHIVE on a database.
1077115The CREDENTIAL option cannot be used with the FEDERATED_SERVICE_ACCOUNT = ON option.
1077215There are multiple REMOTE_DATA_ARCHIVE_OVERRIDE hints specified on the same table or view reference. Remove the extra REMOTE_DATA_ARCHIVE_OVERRIDE hint(s) and resubmit the query.
1077315The REMOTE_DATA_ARCHIVE_OVERRIDE hint is not applicable to object ‘%.*ls’ because it is not a table with REMOTE_DATA_ARCHIVE enabled. Remove the REMOTE_DATA_ARCHIVE_OVERRIDE hint and resubmit the statement.
1077415Incorrect WHERE clause for filtered index.
1077516Object ‘%.*ls’ is not a memory optimized table or a natively compiled inline table-valued function and cannot be accessed from a natively compiled module.
1077616Triggers on non-memory optimized tables cannot use WITH NATIVE_COMPILATION.
1077716Triggers on memory-optimized tables must use WITH NATIVE_COMPILATION.
1077816Foreign key relationships between memory optimized tables and non-memory optimized tables are not supported.
1077916The durability option ‘schema_only’ is supported only with memory optimized tables.
1078016There is no primary key in the referenced table ‘%.*ls’ that matches the referencing column list in the foreign key ‘%.*ls’. Foreign keys in memory-optimized tables must reference primary keys.
1078116Querytraceon %d and optimizer hint ‘%.*ls’ specify conflicting behaviors. Remove one of them and rerun the query.
1078216BEGIN ATOMIC is supported only in natively compiled modules.
1078316The body of a natively compiled module must be an ATOMIC block.
1078416The WITH clause of BEGIN ATOMIC statement must specify a value for the option ‘%ls’.
1078515The %S_MSG ‘%ls’ is supported only with %S_MSG.
1078616The ALTER AVAILABILITY GROUP command failed because it contained multiple MODIFY REPLICA options: %ls.  Enter a separate ALTER AVAILABILITY GROUP … MODIFY REPLICA command for each replica option that you want to modify.
1078716The REPEATABLEREAD and SERIALIZABLE hints are not permitted on Hekaton tables with columnstore indexes.
1078815The option ‘%ls’ is not supported with table types.
1078915The option ‘%ls’ must be specified for index ‘%.*ls’ on table ‘%.*ls’. It is required for hash indexes.
1079015The option ‘%ls’ can be specified only for hash indexes.
1079115Hash indexes are permitted only in memory optimized tables.
1079215When used in a natively compiled module, the function ‘%.*ls’ cannot appear outside of a catch block.
1079316Both an index and a PRIMARY KEY constraint have been defined inline, with the definition of column ‘%.*ls’, table ‘%.*ls’. Defining both an index and a PRIMARY KEY constraint inline with the column definition is not allowed.
1079415The %S_MSG ‘%ls’ is not supported with %S_MSG.
1079515The variable ‘%.*ls’ was declared as not null, and must be declared with an initial value.
1079615The SCHEMABINDING option is supported only for natively compiled modules, and is required for those modules.
1079715Only one MEMORY_OPTIMIZED_DATA filegroup is allowed per database.
1079816This is not a valid data compression setting for this object. It can only be used with columnstore indexes. Please choose NONE, PAGE, or ROW compression.
1079916This is not a valid data compression setting for a columnstore index. Please choose COLUMNSTORE or COLUMNSTORE_ARCHIVE compression.
1080016The listener for the WSFC resource ‘%.*ls’ failed to start, and returned error code %d, ‘%.*ls’. For more information about this error code, see “System Error Codes” in the Windows Development Documentation.
1080116Failed to stop the listener for Windows Failover Cluster resource ‘%.*ls’. Error: %d. %.*ls
1080210Failed to enqueue a task to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is added manually or SQL Server is restarted. SQLOS error code: %d.
1090016Failed to configure resource governor during startup. Check SQL Server error log for specific error messages or check the consistency of master database by running DBCC CHECKCATALOG(‘master’).
1090116User does not have permission to alter the resource governor configuration.
1090216User-defined function ‘%s’ does not exist in master database, or the user does not have permission to access it.
1090316The specified schema name ‘%.*ls’ for classifier user-defined function either does not exist, or the user does not have permission to use it.
1090416Resource governor configuration failed. There are active sessions in workload groups being dropped or moved to different resource pools. Disconnect all active sessions in the affected workload groups and try again.
1090516Could not complete resource governor configuration because there is not enough memory. Reduce the server load or try the operation on a dedicated administrator connection.
1090616The object ‘%.*ls’.’%.*ls’ is not a valid resource governor classifier user-defined function. A valid classifier user-defined function must be schema-bound, return sysname, and have no parameters.
1090716Attribute ‘%.*ls’ with value of %u is greater than attribute ‘%.*ls’ with value of %u.
1090816Attribute ‘%.*ls’ with value of %u is less than attribute ‘%.*ls’ with value of %u.
1090916The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %u including predefined resource pools.
1091016The operation could not be completed.  The specified ‘%.*ls’ value, %u, causes the sum of minimums on all resource pools on scheduler %u to exceed 100 percent. Reduce the value for one or more pools, or change pool affinity, so that the sum is less than or equal to 100.
1091116Requested operation cannot be performed because the resource pool ‘%.*ls’ does not exist.
1091216The operation could not be completed. Dropping predefined %S_MSG is not allowed.
1091316Users are not allowed to %S_MSG the workload group ‘%.*ls’ in the ‘%.*ls’ resource pool.
1091416The name of the %S_MSG ‘%.*ls’ cannot begin with # of ##.
1091516The operation could not be completed. Altering ‘%.*ls’ %S_MSG is not allowed.
1091616Cannot drop resource pool ‘%.*ls’ because it contains workload group ‘%.*ls’. Drop or remove all workload groups using this resource pool before dropping it.
1091716ALTER WORKLOAD GROUP failed.  Either a ‘WITH’ or ‘USING’ clause must be specified.
1091816Cannot create %S_MSG ‘%.*ls’ because it already exists.
1091916An error occurred while reading the resource governor configuration from master database. Check the integrity of master database or contact the system administrator.
1092016Cannot %S_MSG user-defined function ‘%.*ls’. It is being used as a resource governor classifier.
1092116The ‘%.*ls’ %S_MSG cannot be moved out of ‘%.*ls’ %S_MSG.
1092216%ls failed. Rerun the statement.
1092316%ls failed.  The resource governor is not available in this edition of SQL Server. You can manipulate resource governor metadata but you will not be able to apply resource governor configuration. Only Enterprise edition of SQL Server supports resource governor.
1092416The pool affinity range is invalid. The lower bound %d must be less than the upper bound %d.
1092516A %S_MSG value was specified more than one time in the pool affinity range list.
1092616The %S_MSG range that specifies %S_MSG %d includes at least one %S_MSG that is not available to the current instance.  The maximum %S_MSG number that is available to this instance is %d.
1092716The operation could not be completed.  The specified ‘%.*ls’ value, %u, causes the sum of minimums on all workload groups using resource pool ‘%.*ls’ to exceed 100 percent. Reduce the value or modify other workload groups so that the sum is less than or equal to 100.
1092816Resource ID : %d. The %ls limit for the database is %d and has been reached. See ‘http://go.microsoft.com/fwlink/?LinkId=267637’ for assistance.
1093016The service is currently too busy. Please try again later.
1093116Cannot drop resource pool ‘%.*ls’ because it is bound to a database. Remove all bindings to this resource pool before dropping it.
1093216Resource governor configuration failed, because there is an active database in the resource pool being dropped. Take the database offline and try again.
1093316A %S_MSG with id %d does not exist on this system.  Use sys.dm_os_schedulers to locate valid %S_MSGs for this system.
1093416Requested operation cannot be performed because the external resource pool ‘%.*ls’ does not exist.
1093516External resource pool does not allow more than one processor group.
1093616Resource ID : %d. The %ls limit for the elastic pool is %d and has been reached. See ‘http://go.microsoft.com/fwlink/?LinkId=267637’ for assistance.
1093716Default workload group does not allow to alter attribute ‘%.*ls’.
1096116The request has been aborted because its CPU usage exceeds the maximum configured limit for the workload group.
1098110Resource governor reconfiguration succeeded.
1098216Failed to run resource governor classifier user-defined function ‘%.*ls’. Last error %u, state %u. See previous errors in SQL Server error log from session ID %ld for details.  Classifier elapsed time: %I64u ms.
1098316Resource governor ‘%ls’ operation was canceled by user.
1098416Resource governor reconfiguration failed.
1098510Resource governor reconfiguration encountered an issue (HRESULT code : 0x%lx, reason: %ls), while sending active external resource pool ids to launchpad. This will not fail reconfigure.
1100016Unknown status code for this column.