HomeSQL ServerSQL Server Error Messages 4001 to 5000

SQL Server Error Messages 4001 to 5000

In this post, we’ll list out the SQL Server Error Messages from the error codes 4001 to 5000 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 4001 to 5000

ErrorCodeSeverityErrorMessage
400110Client sends a sp_reset_connection while there is still pending requests, server is disconnecting.
400216The incoming tabular data stream (TDS) protocol stream is incorrect. The stream ended unexpectedly.
400416Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier.
400516Cannot update columns from more than one underlying table in a single update call.
400616You cannot delete rows from more than one underlying table in a single delete call.
400716Cannot update or insert column “%.*ls”. It may be an expression.
400816The data types varchar(max), nvarchar(max), varbinary(max), and XML cannot be used in the compute clause by client driver versions earlier than SQL Server 2005.  Please resubmit the query using a more recent client driver.
400916The incoming tabular data stream (TDS) protocol stream is incorrect. The TDS headers contained errors.
401016The incoming tabular data stream (TDS) protocol stream is incorrect. The Query Notification TDS header contained errors.
401116The incoming tabular data stream (TDS) protocol stream is incorrect. The MARS TDS header contained errors.
401216An invalid tabular data stream (TDS) collation was encountered.
401316The incoming tabular data stream (TDS) protocol stream is incorrect. The multiple active result sets (MARS) TDS header is missing.
401420A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: %d, output error: %d).
401516Language requested in login ‘%.*ls’ is not an official name on this SQL Server. Using server-wide default %.*ls instead.
401616Language requested in ‘login %.*ls’ is not an official name on this SQL Server. Using user default %.*ls instead.
401716Neither the language requested in ‘login %.*ls’ nor user default language %.*ls is an official language name on this SQL Server. Using server-wide default %.*ls instead.
401816User default language %.*ls is not an official language name on this SQL Server. Using server-wide default %.*ls instead.
401916Language requested in login ‘%.*ls’ is not an official language name on this SQL Server. Login fails.
402016Default date order ‘%.*ls’ for language %.*ls is invalid. Using mdy instead.
402116Resetting the connection results in a different state than the initial login. The login fails.
402216Bulk load data was expected but not sent. The batch will be terminated.
402716Mount tape for %hs of database ‘%ls’ on tape drive ‘%ls’.
402816End of tape has been reached. Remove tape ‘%ls’ and mount next tape for %hs of database ‘%ls’.
403010The medium on device ‘%ls’ expires on %hs and cannot be overwritten.
403510Processed %I64d pages for database ‘%ls’, file ‘%ls’ on file %d.
403716The user-specified MEDIANAME “%.*ls” does not match the MEDIANAME “%ls” of the device “%ls”.
403816Cannot find file ID %d on device ‘%ls’.
406011Cannot open database “%.*ls” requested by the login. The login failed.
406111Neither the database “%.*ls” requested by the login nor the user default database could be opened. The master database is being used instead.
406211Cannot open user default database. Using master database instead.
406311Cannot open database “%.*ls” that was requested by the login. Using the user default database “%.*ls” instead.
406411Cannot open user default database. Login failed.
406516User is trying to use ‘%.*ls’ through ODS, which is not supported any more.
406616Type IDs larger than 65535 cannot be sent to clients shipped in SQL Server 2000 or earlier.
406716CLR type serialization failed because an invalid cookie was specified.
406820sp_resetconnection was sent as part of a remote procedure call (RPC) batch, but it was not the last RPC in the batch. This connection will be terminated.
406916The final value of the output parameter was null, and could not be sent to a 6.5 client expecting the parameter to be non-nullable.
407016More than 255 columns were specified in the COMPUTE clause, and this metadata cannot be sent to a SQL Server version 6.5 client.
407110The XP callback function ‘%.*ls’ failed in extended procedure ‘%.*ls’ because it was executed within an INSERT-EXEC statement which does not allow the extended procedure to send information other than result set.
407210The XP callback function ‘%.*ls’ failed in extended procedure ‘%.*ls’ because the extended procedure is called inside an UDF which doesn’t allow sending data.
407316A return value of data type varchar(max), nvarchar(max), varbinary(max), XML or other large object type can not be returned to client driver versions earlier than SQL Server 2005.  Please resubmit the query using a more recent client driver.
407416Client drivers do not accept result sets that have more than 65,535 columns.
407516The USE database statement failed because the database collation %.*ls is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
407616The ALTER DATABASE statement failed because the database collation %.*ls is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
407720The statement failed because the sql_variant value uses collation %.*ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
407816The statement failed because column ‘%.*ls’ (ID=%d) uses collation %.*ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
407916The statement failed due to arithmetic overflow when sending data stream.
408016The incoming tabular data stream (TDS) protocol stream is incorrect. The TRACE TDS header contained errors.
408116The parameter ‘%.*ls’ was deduced to be a table-valued parameter, which cannot be sent by client driver versions earlier than SQL Server 2008. Please resubmit the query using a more recent client driver.
408216Cannot recover the session state requested by the login.
408316The connection was recovered and rowcount in the first query is not available. Please execute another query to get a valid rowcount.
410116Aggregates on the right side of an APPLY cannot reference columns from the left side.
410215The READPAST lock hint is only allowed on target tables of UPDATE and DELETE and on tables specified in an explicit FROM clause.
410315%.*ls: Temporary views are not allowed.
410416The multi-part identifier “%.*ls” could not be bound.
410516User-defined functions, partition functions, and column references are not allowed in expressions in this context.
410716Inserting into remote tables or views is not allowed by using the BCP utility or by using BULK INSERT.
410816Windowed functions can only appear in the SELECT or ORDER BY clauses.
410916Windowed functions cannot be used in the context of another windowed function or aggregate.
411016The argument type “%s” is invalid for argument %d of “%s”.
411116The CREATE SCHEMA statement should be followed by a name or authorization keyword.
411216The function ‘%.*ls’ must have an OVER clause with ORDER BY.
411316The function ‘%.*ls’ is not a valid windowing function, and cannot be used with the OVER clause.
411416The function ‘%.*ls’ takes exactly %d argument(s).
411516The reference to column “%.*ls” is not allowed in an argument to a TOP, OFFSET, or FETCH clause. Only references to columns at an outer scope or standalone expressions and subqueries are allowed here.
411616The function ‘ntile’ takes only a positive int or bigint expression as its input.
411716Cannot retrieve table data for the query operation because the table “%.*ls” schema is being altered too frequently. Because the table “%.*ls” contains a computed column, changes to the table schema require a refresh of all table data. Retry the query operation, and if the problem persists, use SQL Server Profiler to identify what schema-altering operations are occurring.
411816An invalid expression was specified in the FOR UPDATE clause.
411916Default values cannot be assigned to property setters of columns with a CLR type.
412016A user-defined function name cannot be prefixed with a database name in this context.
412116Cannot find either column “%.*ls” or the user-defined function or aggregate “%.*ls”, or the name is ambiguous.
412216Remote table-valued function calls are not allowed.
412416The parameters supplied for the batch are not valid.
412616No full-text indexed columns were found.
412716At least one of the arguments to COALESCE must be an expression that is not the NULL constant.
412816An internal error occurred during remote query execution. Contact your SQL Server support professional and provide details about the query you were trying to run.
412916The inline function “%.*ls” cannot take correlated parameters or subqueries because it uses a full-text operator.
413016A duplicate hint was specified for the BULK rowset.
413116A compile-time literal value is specified more than once for the variable “%.*ls” in one or more OPTIMIZE FOR clauses.
413216The value specified for the variable “%.*ls” in the OPTIMIZE FOR clause could not be implicitly converted to that variable’s type.
413316Only a scalar expression may be specified as the argument to the RETURN statement.
413416Metadata stored on disk for computed column ‘%.*ls’ in table ‘%.*ls’ did not match the column definition. In order to avoid possible index corruption, please drop and recreate this computed column.
413516Synonym ‘%.*ls’ is defined over queue ‘%.*ls’. Synonyms on queues are not allowed.
413616The hint ‘%.*ls’ cannot be used with the hint ‘%.*ls’.
413716A format file cannot be specified together with SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB option.
413816Conflicting locking hints are specified for table “%.*ls”. This may be caused by a conflicting hint specified for a view.
413916Cannot process the query because it references the common language runtime (CLR) table-valued function “%.*ls” with a hint through view “%.*ls”.
414015The READCOMMITTEDLOCK lock hint is not allowed on the target table of an INSERT statement.
414116Nested CLR type updates are not allowed.
414216Aggregates are not allowed in the RECEIVE list.
414316The bulk openrowset provider is not a valid target for %.*ls.
414416The hint ‘%.*ls’ is not allowed when inserting into remote tables.
414515An expression of non-boolean type specified in a context where a condition is expected, near ‘%.*ls’.
414616Statistics can only be created on columns.
414816XML methods are not allowed in a GROUP BY clause.
415016Hints are not allowed on recursive common table expression (CTE) references. Consider removing hint from recursive CTE reference ‘%.*ls’.
415116The type of the first argument to NULLIF cannot be the NULL constant because the type of the first argument has to be known.
415216Type “%.*ls” is not a CLR type.
415316Cannot treat data type “%ls” as data type “%ls”.
415416UNNEST can only take an expression of type multiset.
415515The SELECT list for the nested INSERT statement can only contain one item.
415616The target of nested insert, nested update, or nested delete must be of type multiset.
415716%.*ls is not a valid property, field, or method.
415816The field “%.*ls” is referenced more than once in the set list, either directly or through a property.
415916Delayed CLR type instances require local base table column as an argument.
416016Could not find suitable key in table ‘%.*ls’ for use in delayed CLR type fetching.
416116Only CLR types are allowed in delayed CLR type fetching.
416216A PROB_MATCH table can only be used inside of a PROB_MATCH query.
416316A GROUP BY clause is required in a PROB_MATCH query.
416416A GROUP BY clause in a PROB_MATCH query can only have key columns, and needs to include all the key columns.
416516The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same constant and variable.
416616Invalid PROB_MATCH subquery.
416716Multiple PROB_MATCH subqueries can only refer to the same base table.
416816Invalid PROB_MATCH project item in the PROB_MATCH SELECT list.
416916Applying TREAT more than once to the same expression is not allowed in a full-text property reference.
417016The (ANY) specification can only be applied to expressions of type multiset.
417116Alias was not specified for an aggregate in the PROB_MATCH SELECT list.
417216Incorrect use of full-text %s.
417316%.*s is not a valid scoring function name.
417416Delayed CLR type instantiation fetch value query may only reference column of a large object or large value type.
417516Nested updates cannot be performed on CLR types that are not Format.Structured.
417616Too many parameters were specified for FULLTEXTTABLE of type “Simple”. The maximum number of parameters is %d.
417716The FROM clause of a PROB_MATCH query must consist of a single derived table.
418416Cannot retrieve table data for the query operation because the table “%.*ls” schema is being altered too frequently. Because the table “%.*ls” contains a filtered index or filtered statistics, changes to the table schema require a refresh of all table data. Retry the query operation, and if the problem persists, use SQL Server Profiler to identify what schema-altering operations are occurring.
418516This action cannot be performed on a system type.
418616Column ‘%ls.%.*ls’ cannot be referenced in the OUTPUT clause because the column definition contains a subquery or references a function that performs user or system data access. A function is assumed by default to perform data access if it is not schemabound. Consider removing the subquery or function from the column definition or removing the column from the OUTPUT clause.
418716Data type %ls of receiving variable cannot store all values of the data type %ls of column ‘%.*ls’ without data loss.
418816Column or parameter ‘%.*ls’ has type ‘%ls’ and collation ‘%.*ls’. The legacy LOB types do not support UTF-8 or UTF-16 encodings. Use types varchar(max), nvarchar(max) or a collation which does not have the _SC or _UTF8 flags.
418916Cannot convert to text/ntext or collate to ‘%.*ls’ because these legacy LOB types do not support UTF-8 or UTF-16 encodings. Use types varchar(max), nvarchar(max) or a collation which does not have the _SC or _UTF8 flags.
419016PIVOT operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
419116Cannot resolve collation conflict for %ls operation.
419216Cannot resolve collation conflict.
419316‘%.*ls’ is not a valid window frame and cannot be used with the OVER clause.
419415RANGE is only supported with UNBOUNDED and CURRENT ROW window frame delimiters.
419516The reference to column “%.*ls” is not allowed in an argument to the NTILE function. Only references to columns at an outer scope or standalone expressions and subqueries are allowed here.
419616Column ‘%ls.%.*ls’ cannot be referenced in the OUTPUT clause because the column definition contains an expression using a window function.
419716An internal query compilation error occurred during binding.
419816Collation ‘%.*ls’ is supported on Unicode data types only. Unicode-only collations cannot be used to specify partition function parameters.
419916Argument value %d is invalid for argument %d of %ls function.
420216BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable.
420816The statement %hs is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
421216Cannot back up the log of the master database. Use BACKUP DATABASE instead.
421416BACKUP LOG cannot be performed because there is no current database backup.
421510The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure the Log Reader Agent or capture job is running or use sp_repldone to mark transactions as distributed or captured.
421710BACKUP LOG cannot modify the database because the database is read-only. The backup will continue, although subsequent backups will duplicate the work of this backup.
421816Bulk-logged operations exist in the database. Perform a BACKUP LOG.
421910The log backup chain is broken. You must perform a full database backup before you can perform a log backup.
422016Cannot back up the log of the model database with NORECOVERY option.
422116Login to read-secondary failed due to long wait on ‘HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING’. The replica is not available for login because row versions are missing for transactions that were in-flight when the replica was recycled. The issue can be resolved by rolling back or committing the active transactions on the primary replica. Occurrences of this condition can be minimized by avoiding long write transactions on the primary.
430216The option “%ls” conflicts with online restore. Remove the conflicting option and reissue the command.
430316The roll forward start point is now at log sequence number (LSN) %.*s. Additional roll forward past LSN %.*s is required to complete the restore sequence.
430516The log in this backup set begins at LSN %.*ls, which is too recent to apply to the database. An earlier log backup that includes LSN %.*ls can be restored.
430716The online restore to database ‘%ls’ failed. It may be appropriate to perform an offline restore instead. To force an offline restore, first take the database offline using the ALTER DATABASE statement.
430810The online restore is complete, but WITH NORECOVERY was specified. Use RESTORE WITH RECOVERY to bring affected data online.
430916The state of file “%ls” prevents restoring individual pages.  Only a file restore is currently possible.
431016RESTORE PAGE is not allowed on file “%ls” because the file is not online.
431116RESTORE PAGE is not allowed from backups taken with earlier versions of SQL Server.
431216This log cannot be restored because a gap in the log chain was created. Use more recent data backups to bridge the gap.
431510Some files still require more restore steps before the online restore sequence can be completed.
431816File ‘%ls’ has been rolled forward to LSN %.*ls. This log terminates at LSN %.*ls, which is too early to apply the WITH RECOVERY option. Reissue the RESTORE LOG statement WITH NORECOVERY.
431916A previous restore operation was interrupted and did not complete processing on file ‘%ls’. Either restore the backup set that was interrupted or restart the restore sequence.
432016The file “%ls” was not fully restored by a database or file restore. The entire file must be successfully restored before applying this backup set.
432210This backup set contains records that were logged before the designated point in time. The database is being left in the restoring state so that more roll forward can be performed.
432316A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this RESTORE sequence, all further steps must include the CONTINUE_AFTER_ERROR option.
432616The log in this backup set terminates at LSN %.*ls, which is too early to apply to the database. A more recent log backup that includes LSN %.*ls can be restored.
432716The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled forward to the end of the log.
432816The file “%ls” is missing. Roll forward stops at log sequence number %.*ls. The file is created at log sequence number (LSN) %.*ls, dropped at LSN %.*ls. Restore the transaction log beyond the point in time when the file was dropped, or restore data to be consistent with rest of the database.
432910This log file contains records logged before the designated mark. The database is being left in the Restoring state so you can apply another log file.
433016This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a particular recovery point. Find a compatible backup to restore, or restore the rest of the database to match a recovery point within this backup set, which will restore the database to a different point in time.  For more information about recovery paths, see SQL Server Books Online.
433116The database cannot be recovered because the files have been restored to inconsistent points in time.
433216RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE %ls WITH RECOVERY.
433316The database cannot be recovered because the log was not restored.
433416The named mark does not identify a valid LSN.
433516The specified STOPAT time is too early. All or part of the database is already rolled forward beyond that point.
433616The filegroup “%ls” has been dropped and cannot be restored into the online database.
433716The file “%ls” has been dropped and cannot be restored into the online database.
433816The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use RESTORE DATABASE WITH RECOVERY to recover at the current point.
433910This RESTORE statement successfully performed some actions, but the database could not be brought online because one or more RESTORE steps are needed. Previous messages indicate reasons why recovery cannot occur at this point.
434016The point-in-time clause of this RESTORE statement is restricted for use by RESTORE LOG statements only. Omit the clause or use a clause that includes a timestamp.
434116This log backup contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time.
434216Point-in-time recovery is not possible unless the primary filegroup is part of the restore sequence. Omit the point-in-time clause or restore the primary filegroup.
434316The database has been rolled forward to the end of this backup set and beyond the specified point in time. RESTORE WITH RECOVERY can be used to accept the current recovery point.
434416RESTORE PAGE is not allowed on read-only databases or filegroups.
434510Problems recording information in the msdb..suspect_pages table were encountered. This error does not interfere with any activity except maintenance of the suspect_pages table. Check the error log for more information.
434616RESTORE PAGE is not allowed with databases that use the simple recovery model or have broken the log backup chain.
434716The current restore sequence was previously interrupted during the transition to the online state. RESTORE DATABASE WITH RECOVERY can be used to complete the transition to online.
434816The online restore to database ‘%ls’ failed. It may be appropriate to perform an offline restore instead. An offline restore is initiated by using BACKUP LOG WITH NORECOVERY.
434916The log in this backup set begins at LSN %.*ls, which is too recent to apply to the database. This restore sequence needs to initialize the log to start at LSN %.*ls. Reissue the RESTORE LOG statement using an earlier log backup.
435016The list of pages provided with the RESTORE PAGE statement is incorrectly formatted. Prior to the problem %d pages were correctly identified. The problem was hit at character offset %d. Check that all pages are identified by numeric <file>:<page> pairs with commas separating each pair.  For example: PAGE=’1:57,2:31′.
435116Backups taken on earlier versions of SQL Server are not supported by fn_dump_dblog.
435216RESTORE LOG is not supported from this data backup because file ‘%ls’ is too old. Use a regular log backup to continue the restore sequence.
435316Conflicting file relocations have been specified for file ‘%.*ls’. Only a single WITH MOVE clause should be specified for any logical file name.
435410The file ‘%.*ls’ of restored database ‘%ls’ is being left in the defunct state because the database is being upgraded from a prior version. Piecemeal restore is not supported when an upgrade is involved.
435516The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATABASE <x> FROM DATABASE_SNAPSHOT = <y>.
435610Restore is complete on database ‘%ls’.  The database is now available.
435716Restore cannot take ‘%ls’ offline because changes exist that require a log backup. Take a log backup and then retry the RESTORE.
435816The database can not be brought online because file ‘%ls’ is currently restored to LSN %.*ls but must be restored to LSN %.*ls.
435916The STOPAT option cannot be used with this partial restore sequence because one or more FILESTREAM filegroups are not included. The CONTINUE_AFTER_ERROR option can be used to force the recovery, but this should only be used if you do not intend to subsequently restore the FILESTREAM filegroups.
436016RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted.
436116Redo LSN has not changed for a while. Abandoning the wait as this could be a deadlock. Redo LSN %.*ls, HkRecoveryLsn %.*ls.
440316Cannot update the view or function ‘%.*ls’ because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator.
440516View or function ‘%.*ls’ is not updatable because the modification affects multiple base tables.
440616Update or insert of view or function ‘%.*ls’ failed because it contains a derived or constant field.
440819Too many tables. The query and the views or functions in it exceed the limit of %d tables. Revise the query to reduce the number of tables.
441316Could not use view or function ‘%.*ls’ because of binding errors.
441416Could not allocate ancillary table for view or function resolution. The maximum number of tables in a query (%d) was exceeded.
441516View ‘%.*ls’ is not updatable because either it was created WITH CHECK OPTION or it spans a view created WITH CHECK OPTION and the target table is referenced multiple times in the resulting query.
441616UNION ALL view ‘%.*ls’ is not updatable because the definition contains a disallowed construct.
441716Derived table ‘%.*ls’ is not updatable because the definition contains a UNION operator.
441816Derived table ‘%.*ls’ is not updatable because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator.
442016Derived table ‘%.*ls’ is not updatable because the modification affects multiple base tables.
442116Derived table ‘%.*ls’ is not updatable because a column of the derived table is derived or constant.
442216View ‘%.*ls’ has an INSTEAD OF UPDATE trigger and cannot be a target of an UPDATE FROM statement.
442316View ‘%.*ls’ has an INSTEAD OF DELETE trigger and cannot be a target of a DELETE FROM statement.
442416Joined tables cannot be specified in a query containing outer join operators. View or function ‘%.*ls’ contains joined tables.
442516Cannot specify outer join operators in a query containing joined tables. View or function ‘%.*ls’ contains outer join operators.
442616View ‘%.*ls’ is not updatable because the definition contains a UNION operator.
442716Cannot update the view “%.*ls” because it or a view it references was created with WITH CHECK OPTION and its definition contains a TOP or OFFSET clause.
442916View or function ‘%.*ls’ contains a self-reference. Views or functions cannot reference themselves directly or indirectly.
443010Warning: Index hints supplied for view ‘%.*ls’ will be ignored.
443116Partitioned view ‘%.*ls’ is not updatable because table ‘%.*ls’ has a timestamp column.
443216Partitioned view ‘%.*ls’ is not updatable because table ‘%.*ls’ has a DEFAULT constraint.
443316Cannot INSERT into partitioned view ‘%.*ls’ because table ‘%.*ls’ has an IDENTITY constraint.
443416Partitioned view ‘%.*ls’ is not updatable because table ‘%.*ls’ has an INSTEAD OF trigger.
443516Partitioned view ‘%.*ls’ is not updatable because a value was not specified for partitioning column ‘%.*ls’.
443616UNION ALL view ‘%.*ls’ is not updatable because a partitioning column was not found.
443716Partitioned view ‘%.*ls’ is not updatable as the target of a bulk operation.
443816Partitioned view ‘%.*ls’ is not updatable because it does not deliver all columns from its member tables.
443916Partitioned view ‘%.*ls’ is not updatable because the source query contains references to partition table ‘%.*ls’.
444016UNION ALL view ‘%.*ls’ is not updatable because a primary key was not found on table ‘%.*ls’.
444116Partitioned view ‘%.*ls’ is not updatable because the table ‘%.*ls’ has an index on a computed column.
444216UNION ALL view ‘%.*ls’ is not updatable because base table ‘%.*ls’ is used multiple times.
444316UNION ALL view ‘%.*ls’ is not updatable because column ‘%.*ls’ of base table ‘%.*ls’ is used multiple times.
444416UNION ALL view ‘%.*ls’ is not updatable because the primary key of table ‘%.*ls’ is not included in the union result.
444516UNION ALL view ‘%.*ls’ is not updatable because the primary key of table ‘%.*ls’ is not unioned with primary keys of preceding tables.
444616Cannot update the UNION ALL view “%.*ls” because the definition of column “%.*ls” of view “%.*ls” is used by another view column.
444716View ‘%.*ls’ is not updatable because the definition contains a set operator.
444816Cannot INSERT into partitioned view ‘%.*ls’ because values were not supplied for all columns.
444916Using defaults is not allowed in views that contain a set operator.
445016Cannot update partitioned view ‘%.*ls’ because the definition of the view column ‘%.*ls’ in table ‘%.*ls’ has an IDENTITY constraint.
445116Views referencing tables on multiple servers are not updatable in the edition of this SQL Server instance ‘%.*ls’. See books online for more details on feature support in different SQL Server editions.
445216Cannot UPDATE partitioning column ‘%.*ls’ of view ‘%.*ls’ because the table ‘%.*ls’ has a CASCADE DELETE or CASCADE UPDATE constraint.
445316Cannot UPDATE partitioning column ‘%.*ls’ of view ‘%.*ls’ because the table ‘%.*ls’ has a INSERT, UPDATE or DELETE trigger.
445416Cannot update the partitioned view “%.*ls” because the partitioning columns of its member tables have mismatched types.
445616The partitioned view “%.*ls” is not updatable because one or more of the non-partitioning columns of its member tables have mismatched types.
445716The attempted insert or update of the partitioned view failed because the value of the partitioning column does not belong to any of the partitions.
445816The partitioned view “%.*ls” is not updatable because one or more of the partioned tables is a Hekaton table and the partitioned column is being updated.
450216View or function ‘%.*ls’ has more column names specified than columns defined.
450316Could not create schemabound %S_MSG ‘%.*ls’ because it references an object in another database.
450416Could not create %S_MSG ‘%.*ls’ because CLR type ‘%.*ls’ does not exist in the target database ‘%.*ls’.
450516CREATE VIEW failed because column ‘%.*ls’ in view ‘%.*ls’ exceeds the maximum of %d columns.
450616Column names in each view or function must be unique. Column name ‘%.*ls’ in view or function ‘%.*ls’ is specified more than once.
450816Views or functions are not allowed on temporary tables. Table names that begin with ‘#’ denote temporary tables.
451016Could not perform CREATE VIEW because WITH %ls was specified and the view is not updatable.
451116Create View or Function failed because no column name was specified for column %d.
451216Cannot schema bind %S_MSG ‘%.*ls’ because name ‘%.*ls’ is invalid for schema binding. Names must be in two-part format and an object cannot reference itself.
451316Cannot schema bind %S_MSG ‘%.*ls’. ‘%.*ls’ is not schema bound.
451416CREATE FUNCTION failed because a column name is not specified for column %d.
451516CREATE FUNCTION failed because column ‘%.*ls’ in function ‘%.*ls’ exceeds the maximum of %d columns.
451616Cannot schema bind function ‘%.*ls’ because it contains an EXECUTE statement.
451716Service queue object cannot be used in schemabinding expressions. ‘%.*ls’ is a service queue.
451916Cannot %S_MSG %S_MSG ‘%.*ls’ on view ‘%.*ls’ because it is a system generated view that was created for optimization purposes.
452016Cannot disable index on view ‘%.*ls’ because it is a system generated view that was created for optimization purposes.
452116Cannot use object ‘%.*ls’ with autodrop object attribute in schemabinding expressions because it is a system generated view that was created for optimization purposes.
452216Cannot alter view ‘%.*ls’ because it is a system generated view that was created for optimization purposes.
452316Cannot create trigger on view ‘%.*ls’ because it is a system generated view that was created for optimization purposes.
452416Cannot alter view ‘%.*ls’ because it has snapshot materialization.
452516Cannot use hint ‘%ls’ on view ‘%.*ls’ that has snapshot materialization before the view is refreshed.
452616Cannot use isolation level table hint on view ‘%.*ls’ that has snapshot materialization without EXPAND VIEWS query hint.
452716Cannot ALTER VIEW ‘%.*ls’ with SNAPSHOT attribute. Use CREATE VIEW instead.
460214Only members of the sysadmin role can grant or revoke the CREATE DATABASE permission.
460416There is no such user or group ‘%.*ls’ or you do not have permission.
460616Granted or revoked privilege %ls is not compatible with object.
461016You can only grant or revoke permissions on objects in the current database.
461116To revoke or deny grantable privileges, specify the CASCADE option.
461316Grantor does not have GRANT permission.
461516Invalid column name ‘%.*ls’.
461616You cannot perform this operation for the resource database.
461716Cannot grant, deny or revoke permissions to or from special roles.
461816You do not have permission to use %.*ls in the AS clause.
461916CREATE DATABASE permission can only be granted in the master database.
462016All permissions in a grant/deny/revoke statement should be at the same scope (e.g., server or database)
462116Permissions at the server scope can only be granted when the current database is master
462216Permissions at the server scope can only be granted to logins
462316The all permission has been deprecated and is not available for this class of entity
462416Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.
462516There is no such server principal %.*s or you do not have permission.
462716Cannot grant, deny, or revoke the connect database permission to application roles.
462816The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
462916Permissions on server scoped catalog views or system stored procedures or extended stored procedures can be granted only when the current database is master.
463016The permission ‘%.*ls’ is not supported in this version of SQL Server. Alternatively, use the %.*ls level ‘%.*ls’ permission.
463116The permission ‘%.*ls’ is not supported in this version of SQL Server.
463216The permission ‘%.*ls’ is not supported in this version of SQL Server. Alternatively, use the %.*ls level ‘%.*ls’ permission.
470116Cannot find the object “%.*ls” because it does not exist or you do not have permissions.
470716Could not truncate object ‘%.*ls’ because it or one of its indexes resides on a READONLY filegroup ‘%.*ls’.
470816Could not truncate object ‘%.*ls’ because it is not a table.
470916You are not allowed to truncate the system table ‘%.*ls’.
471016Could not truncate object ‘%.*ls’ because it or one of its indexes resides on an offline filegroup ‘%.*ls’.
471116Cannot truncate table ‘%.*ls’ because it is published for replication or enabled for Change Data Capture.
471216Cannot truncate table ‘%.*ls’ because it is being referenced by a FOREIGN KEY constraint.
480116Insert bulk is not supported over this access protocol.
480216The SINGLE_LOB, SINGLE_CLOB, and SINGLE_NCLOB options are mutually exclusive with all other options.
480321The bulk copy (bcp) client has sent a row length of %d. This is not a valid size. The maximum row size is %d. Use a supported client application programming interface (API).
480421While reading current row from host, a premature end-of-message was encountered–an incoming data stream was interrupted when the server expected to see more data. The host program may have terminated. Ensure that you are using a supported client application programming interface (API).
480517The front-end tool you are using does not support bulk load from host. Use the supported tools for this command.
480616SINGLE_CLOB requires a double-byte character set (DBCS) (char) input file. The file specified is Unicode.
480721The bulk copy (bcp) client sent a row length of %d. This size is not valid. The minimum row size is %d. Use a supported client application programming interface (API).
480816Bulk copy operations cannot trigger bulk load statements.
480916SINGLE_NCLOB requires a UNICODE (widechar) input file. The file specified is not Unicode.
481016Expected the TEXT token in data stream for bulk copy of text or image data.
481116Expected the column offset in data stream for bulk copy of text or image data.
481216Expected the row offset in data stream for bulk copy of text or image data.
481316Expected the text length in data stream for bulk copy of text, ntext, or image data.
481416Bulk copy into a partitioned table is not supported for down-level clients.
481516Received an invalid column length from the bcp client for colid %d.
481616Invalid column type from bcp client for colid %d.
481716Could not bulk load. The sorted column ‘%.*ls’ is not valid. The ORDER hint is ignored.
481816Could not bulk load. The sorted column ‘%.*ls’ was specified more than once. The ORDER hint is ignored.
481916Cannot bulk load. The bulk data stream was incorrectly specified as sorted or the data violates a uniqueness constraint imposed by the target table. Sort order incorrect for the following two rows: primary key of first row: %s, primary key of second row: %s.
482016Cannot bulk load. Unknown version of format file “%s”.
482116Cannot bulk load. Error reading the number of columns from the format file “%s”.
482216Cannot bulk load. Invalid number of columns in the format file “%s”.
482316Cannot bulk load. Invalid column number in the format file “%s”.
482416Cannot bulk load. Invalid data type for column number %d in the format file “%s”.
482516Cannot bulk load. Invalid prefix for column number %d in the format file “%s”.
482616Cannot bulk load. Invalid column length for column number %d in the format file “%s”.
482716Cannot bulk load. Invalid column terminator for column number %d in the format file “%s”.
482816Cannot bulk load. Invalid destination table column number for source column %d in the format file “%s”.
482916Cannot bulk load. Error reading the destination table column name for source column %d in the format file “%s”.
483010Bulk load: DataFileType was incorrectly specified as char. DataFileType will be assumed to be widechar because the data file has a Unicode signature.
483110Bulk load: DataFileType was incorrectly specified as widechar. DataFileType will be assumed to be char because the data file does not have a Unicode signature.
483216Bulk load: An unexpected end of file was encountered in the data file.
483316Bulk load: Version mismatch between the provider dynamic link library and the server executable.
483416You do not have permission to use the bulk load statement.
483516Bulk copying into a table with computed columns is not supported for downlevel clients.
483610Warning: Table “%.*s” is published for merge replication. Reinitialize affected subscribers or execute sp_addtabletocontents to ensure that data added is included in the next synchronization.
483716Cannot bulk copy into a table “%.*s” that is enabled for immediate-updating subscriptions.
483816The bulk data source does not support the SQLNUMERIC or SQLDECIMAL data types.
483916Cannot perform the bulk load. Invalid collation name for source column %d in the format file “%s”.
484016The bulk data source provider string has an invalid %ls property value %ls.
484116The data source name is not a simple object name.
484216The required FormatFile property is missing from the provider string of the server.
484316The bulk data source provider string has a syntax error (‘%lc’) near character position %d.
484416The bulk data source provider string has an unsupported property name (%ls).
484516The bulk data source provider string has a syntax error near character position %d. Expected ‘%lc’, but found ‘%lc’.
484616The bulk data provider failed to allocate memory.
484716Bulk copying into a table with bigint columns is not supported for versions earlier than SQL Server 2000.
484816Bulk copying into a table with sql_variant columns is not supported for versions earlier than SQL Server 2000.
485516Line %d in format file “%ls”: unexpected element “%ls”.
485616Line %d in format file “%ls”: unexpected info item.
485716Line %d in format file “%ls”: Attribute “%ls” could not be specified for this type.
485816Line %d in format file “%ls”: bad value %ls for attribute “%ls”.
485916Line %d in format file “%ls”: required attribute “%ls” is missing.
486016Cannot bulk load. The file “%ls” does not exist or you don’t have file access rights.
486116Cannot bulk load because the file “%ls” could not be opened. Operating system error code %ls.
486216Cannot bulk load because the file “%ls” is incomplete or could not be read. Operating system error code %ls.
486316Bulk load data conversion error (truncation) for row %d, column %d (%ls).
486416Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row %d, column %d (%ls).
486516Cannot bulk load because the maximum number of errors (%d) was exceeded.
486616The bulk load failed. The column is too long in the data file for row %d, column %d. Verify that the field terminator and row terminator are specified correctly.
486716Bulk load data conversion error (overflow) for row %d, column %d (%ls).
486816The bulk load failed. The codepage “%d” is not installed. Install the codepage and run the command again.
486916The bulk load failed. Unexpected NULL value in data file row %d, column %d. The destination column (%ls) is defined as NOT NULL.
487016Cannot bulk load because of an error writing file “%ls”. Operating system error code %ls.
487116Bulk load error while attempting to log errors.
487216Line %d in format file “%ls”: duplicate element id “%ls”.
487316Line %d in format file “%ls”: referencing non-existing element id “%ls”.
487416Line %d in format file “%ls”: duplicate element id reference “%ls”.
487516Invalid column attribute from bcp client for colid %d.
487616The Bulk Insert operation of SQL Server Destination has timed out. Please consider increasing the value of Timeout property on the SQL Server Destination in the dataflow.
487716Error parsing DTS stream when reading row %d, column %d.
487816Invalid quote character specified for bulk load. Quote character can be one single byte or Unicode character.
487916Bulk load failed due to invalid column value in CSV data file %ls in row %d, column %d.
488016Cannot bulk load. When you use the FIRSTROW and LASTROW parameters, the value for FIRSTROW cannot be greater than the value for LASTROW.
488110Note: Bulk Insert through a view may result in base table default values being ignored for NULL columns in the data file.
488216Cannot bulk load. A prefix length, field length, or terminator is required for the source column %d in the format file “%s”.
488316The XML reader returned 0x%08X for the info item starting near line %d column %d in format file “%ls”.
488416Unknown error near info item starting near line %d column %d in format file “%ls”.
488516Cannot open file “%ls”. Login using integrated authentication is required.
488616Cannot open the file “%ls”. Operating system error: %ls
488716Cannot open the file “%ls”. Only disk files are supported.
488816Cannot open the file “%ls”. The bulkadmin role membership is required.
488916Cannot open the file “%ls”. A unicode byte-order mark is missing.
489016Insert bulk is not supported in showplan mode.
489116Insert bulk failed due to a schema change of the target table.
489216Bulk insert failed due to a schema change of the target table.
489316Could not bulk load because SSIS file mapping object ‘%ls’ could not be opened. Operating system error code %ls. Make sure you are accessing a local server using integrated authentication.
489421COLMETADATA must be present when using bcp.
489521Unicode data is odd byte size for column %d. Should be even byte size.
489616Invalid column value from bcp client for colid %d.
489716Received an invalid length for chunked LOB data for colid %d.
489816Cannot bulk load CSV file. Invalid field parameters are specified for source column number %d in the format file “%s”. All data fields must be either character or Unicode character with terminator when CSV format is specified.
489916Cannot bulk load CSV file. Invalid terminator is specified for source column number %d in the format file “%s”. All source column terminators must be the same except the last one when CSV format is specified. Only row terminator should be different.
490016The ALTER TABLE SWITCH statement failed for table ‘%.*ls’. It is not possible to switch the partition of a table that has change tracking enabled. Disable change tracking before using ALTER TABLE SWITCH.
490116ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column. Column ‘%.*ls’ cannot be added to non-empty table ‘%.*ls’ because it does not satisfy these conditions.
490216Cannot find the object “%.*ls” because it does not exist or you do not have permissions.
490310Warning: The specified partition %d for the table ‘%.*ls’ was ignored in ALTER TABLE SWITCH statement because the table is not partitioned.
490416ALTER TABLE SWITCH statement failed. The specified partition %d of target table ‘%.*ls’ must be empty.
490516ALTER TABLE SWITCH statement failed. The target table ‘%.*ls’ must be empty.
490616‘%ls’ statement failed. The %S_MSG ‘%.*ls’ is %S_MSG partitioned while index ‘%.*ls’ is %S_MSG partitioned.
490716‘%ls’ statement failed. The %S_MSG ‘%.*ls’ has %d partitions while index ‘%.*ls’ has %d partitions.
490816‘%ls’ statement failed. The range boundary values used to partition the %S_MSG ‘%.*ls’ are different from the range boundary values used for index ‘%.*ls’.
490916Cannot alter ‘%.*ls’ because it is not a table.
491116Cannot specify a partitioned table without partition number in ALTER TABLE SWITCH statement. The table ‘%.*ls’ is partitioned.
491216‘%ls’ statement failed. The columns set used to partition the %S_MSG ‘%.*ls’ is different from the column set used to partition index ‘%.*ls’.
491316ALTER TABLE SWITCH statement failed. The table ‘%.*ls’ has clustered index ‘%.*ls’ while the table ‘%.*ls’ does not have clustered index.
491416The ALTER TABLE SWITCH statement failed. The table “%.*ls” has a disabled clustered index.
491516‘%ls’ statement failed. The parameter type of the partition function used to partition the %S_MSG ‘%.*ls’ is different from the parameter type of the partition function used to partition index ‘%.*ls’.
491616Could not enable or disable the constraint. See previous errors.
491716Constraint ‘%.*ls’ does not exist.
491816ALTER TABLE SWITCH statement failed because the table ‘%.*ls’ has fulltext index on it.
491916PERSISTED attribute cannot be altered on column ‘%.*ls’ because this column is not computed.
492016ALTER TABLE failed because trigger ‘%.*ls’ on table ‘%.*ls’ does not exist.
492116ALTER TABLE failed because trigger ‘%.*ls’ does not belong to table ‘%.*ls’.
492216%ls %.*ls failed because one or more objects access this %S_MSG.
492316ALTER TABLE DROP COLUMN failed because ‘%.*ls’ is the only data column in table ‘%.*ls’. A table must have at least one data column.
492416%ls failed because column ‘%.*ls’ does not exist in table ‘%.*ls’.
492516ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table ‘%.*ls’ with ROWGUIDCOL property.
492616ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table ‘%.*ls’ with ROWGUIDCOL property.
492716Cannot alter column ‘%.*ls’ to be data type %.*ls.
492816Cannot alter column ‘%.*ls’ because it is ‘%ls’.
492916Cannot alter the %S_MSG ‘%.*ls’ because it is being published for replication.
493316Computed column ‘%.*ls’ in table ‘%.*ls’ cannot be persisted because the column depends on a non-schemabound object.
493416Computed column ‘%.*ls’ in table ‘%.*ls’ cannot be persisted because the column does user or system data access.
493516ALTER TABLE ADD COLUMN cannot specify a FILESTREAM filegroup that differs from the existing one.
493616Computed column ‘%.*ls’ in table ‘%.*ls’ cannot be persisted because the column is non-deterministic.
493816ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG ‘%.*ls’ is in filegroup ‘%.*ls’ and partition %d of %S_MSG ‘%.*ls’ is in filegroup ‘%.*ls’.
493916ALTER TABLE SWITCH statement failed. %S_MSG ‘%.*ls’ is in filegroup ‘%.*ls’ and partition %d of %S_MSG ‘%.*ls’ is in filegroup ‘%.*ls’.
494016ALTER TABLE SWITCH statement failed. %S_MSG ‘%.*ls’ is in filegroup ‘%.*ls’ and %S_MSG ‘%.*ls’ is in filegroup ‘%.*ls’.
494116ALTER TABLE SWITCH statement failed because the table ‘%.*ls’ is marked for merge replication.
494216ALTER TABLE SWITCH statement failed because column ‘%.*ls’ at ordinal %d in table ‘%.*ls’ has a different name than the column ‘%.*ls’ at the same ordinal in table ‘%.*ls’.
494316ALTER TABLE SWITCH statement failed because table ‘%.*ls’ has %d columns and table ‘%.*ls’ has %d columns.
494416ALTER TABLE SWITCH statement failed because column ‘%.*ls’ has data type %s in source table ‘%.*ls’ which is different from its type %s in target table ‘%.*ls’.
494516ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same collation in tables ‘%.*ls’ and ‘%.*ls’.
494616ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same persistent attribute in tables ‘%.*ls’ and ‘%.*ls’.
494716ALTER TABLE SWITCH statement failed. There is no identical index in source table ‘%.*ls’ for the index ‘%.*ls’ in target table ‘%.*ls’ .
494816ALTER TABLE SWITCH statement failed. The source table ‘%.*ls’ is in database ‘%.*ls’ while the target table ‘%.*ls’ is in database ‘%.*ls’.
494916ALTER TABLE SWITCH statement failed because the object ‘%.*ls’ is not a user defined table.
495016ALTER TABLE SWITCH statement failed because partition number %d does not exist in table ‘%.*ls’.
495116ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same FILESTREAM storage attribute in tables ‘%.*ls’ and ‘%.*ls’.
495216ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same ANSI trimming semantics in tables ‘%.*ls’ and ‘%.*ls’.
495316ALTER TABLE SWITCH statement failed. The columns set used to partition the table ‘%.*ls’ is different from the column set used to partition the table ‘%.*ls’.
495416ALTER TABLE SWITCH statement failed. The table ‘%.*ls’ has inline limit of %d for text in row data which is different from value %d used by table ‘%.*ls’.
495516ALTER TABLE SWITCH statement failed. The source table ‘%.*ls’ and target table ‘%.*ls’ are same.
495716‘%ls’ statement failed because the expression identifying partition number for the %S_MSG ‘%.*ls’ is not of integer type.
495816ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same ROWGUIDCOL property in tables ‘%.*ls’ and ‘%.*ls’.
495916ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG ‘%.*ls’ has TEXT filegroup ‘%.*ls’ and partition %d of %S_MSG ‘%.*ls’ has TEXT filegroup ‘%.*ls’.
496016ALTER TABLE SWITCH statement failed. Check constraint ‘%.*ls’ in source table ‘%.*ls’ is NOCHECK constraint but the matching check constraint ‘%.*ls’ in target table ‘%.*ls’ is CHECK.
496116ALTER TABLE SWITCH statement failed. Column ‘%.*ls’ in table ‘%.*ls’ is nullable and it is not nullable in ‘%.*ls’.
496316ALTER TABLE SWITCH statement failed. Partition %d is not valid for table ‘%.*ls’.
496416ALTER TABLE SWITCH statement failed. Table ‘%.*ls’ has RULE constraint ‘%.*ls’.  SWITCH is not allowed on tables with RULE constraints.
496516ALTER TABLE SWITCH statement failed. Column ‘%.*ls’ in table ‘%.*ls’ is computed column but the same column in ‘%.*ls’ is not computed.
496616ALTER TABLE SWITCH statement failed. Computed column ‘%.*ls’ defined as ‘%.*ls’ in table ‘%.*ls’ is different from the same column in table ‘%.*ls’ defined as ‘%.*ls’.
496716ALTER TABLE SWITCH statement failed. SWITCH is not allowed because source table ‘%.*ls’ contains primary key for constraint ‘%.*ls’.
496816ALTER TABLE SWITCH statement failed. Target table ‘%.*ls’ has foreign key for constraint ‘%.*ls’ but source table ‘%.*ls’ does not have corresponding key.
496916ALTER TABLE SWITCH statement failed. Foreign key constraint ‘%.*ls’ is disabled in source table ‘%.*ls’ and the corresponding constraint ‘%.*ls’ is enabled in target table ‘%.*ls’.  The source table constraint must be enabled.
497016ALTER TABLE SWITCH statement failed. Target table ‘%.*ls’ has a table level check constraint ‘%.*ls’ but the source table ‘%.*ls’ does not have a corresponding constraint.
497116ALTER TABLE SWITCH statement failed. Target table ‘%.*ls’ has a column level check constraint ‘%.*ls’ but the source table ‘%.*ls’ does not have a corresponding constraint.
497216ALTER TABLE SWITCH statement failed. Check constraints or partition function of source table ‘%.*ls’ allows values that are not allowed by check constraints or partition function on target table ‘%.*ls’.
497316ALTER TABLE SWITCH statement failed. Range defined by partition %d in table ‘%.*ls’ is not a subset of range defined by partition %d in table ‘%.*ls’.
497416ALTER TABLE SWITCH statement failed. Foreign key constraint ‘%.*ls’ is NOCHECK in source table ‘%.*ls’ and the corresponding constraint ‘%.*ls’ is CHECK in target table ‘%.*ls’.  The source table constraint must be in CHECK.
497516ALTER TABLE SWITCH statement failed. Check constraint ‘%.*ls’ in source table ‘%.*ls’ and check constraint ‘%.*ls’ in target table ‘%.*ls’ have different ‘Not For Replication’ settings.
497616ALTER TABLE SWITCH statement failed. Target table ‘%.*ls’ has a check constraint ‘%.*ls’ on an XML column, but the source table ‘%.*ls’ does not have an identical check constraint.
497716ALTER TABLE SWITCH statement failed. Target table ‘%.*ls’ has a check constraint ‘%.*ls’ on a CLR type column, but the source table ‘%.*ls’ does not have an identical check constraint.
497816ALTER TABLE SWITCH statement failed.  The partition %d in table ‘%.*ls’ resides in a read-only filegroup ‘%.*ls’.
497916ALTER TABLE SWITCH statement failed.  The table ‘%.*ls’ resides in a readonly filegroup ‘%.*ls’.
498016ALTER TABLE SWITCH statement failed.  The lobdata of partition %d in table ‘%.*ls’ resides in a readonly filegroup ‘%.*ls’.
498116ALTER TABLE SWITCH statement failed.  The lobdata of table ‘%.*ls’ resides in a readonly filegroup ‘%.*ls’.
498216ALTER TABLE SWITCH statement failed. Check constraints of source table ‘%.*ls’ allow values that are not allowed by range defined by partition %d on target table ‘%.*ls’.
498316ALTER TABLE SWITCH statement failed. Target table ‘%.*ls’ has an XML or spatial index ‘%.*ls’ on it. Only source table can have XML or spatial indexes in the ALTER TABLE SWITCH statement.
498416ALTER TABLE SWITCH statement failed. Target table ‘%.*ls’ and source table ‘%.*ls’ have different vardecimal storage format values. Use stored procedure sp_tableoption to alter the ‘vardecimal storage format’ option for the tables to make sure that the values are the same.
498516ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same nullability attribute in tables ‘%.*ls’ and ‘%.*ls’.
498616ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same CLR type in tables ‘%.*ls’ and ‘%.*ls’.
498716ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same XML Schema Collection in tables ‘%.*ls’ and ‘%.*ls’.
498816Cannot persist computed column ‘%.*ls’. Underlying object ‘%.*ls’ has a different owner than table ‘%.*ls’.
498916Cannot drop the ROWGUIDCOL property for column ‘%.*ls’ in table ‘%.*ls’ because the column is not the designated ROWGUIDCOL for the table.
499016Cannot alter column ‘%.*ls’ in table ‘%.*ls’ to add or remove the FILESTREAM column attribute.
499116Cannot alter NOT FOR REPLICATION attribute on column ‘%.*ls’ in table ‘%.*ls’ because this column is not an identity column.
499216Cannot use table option LARGE VALUE TYPES OUT OF ROW on a user table that does not have any of large value types varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns in it. This option can be applied to tables having large values computed column that are persisted.
499316ALTER TABLE SWITCH statement failed. The table ‘%.*ls’ has different setting for Large Value Types Out Of Row table option as compared to table ‘%.*ls’.
499416Computed column ‘%.*ls’ in table ‘%.*ls’ cannot be persisted because the column type, ‘%.*ls’, is a non-byte-ordered CLR type.
499516Vardecimal storage format cannot be enabled on table ‘%.*ls’ because database ‘%.*ls’ is a system database. Vardecimal storage format is not available in system databases.
499616Change tracking is already enabled for table ‘%.*ls’.
499716Cannot enable change tracking on table ‘%.*ls’. Change tracking requires a primary key on the table. Create a primary key on the table before enabling change tracking.
499816Change tracking is not enabled on table ‘%.*ls’.
499916Cannot enable change tracking on table ‘%.*ls’. Change tracking does not support a primary key of type timestamp on a table.

Leave a Reply

You May Also Like

When dealing with a relational database management system (RDBMS) like SQL Server, compatibility level is an important concept to understand....
In this blog post, let’s learn about the error message “49975 – Unable to load controller client certificate due to...
In this blog post, let’s learn about the error message “49973 – Cannot remove tempdb remote file to local tempdb...