Skip Navigation Links
Home
Functions
Tips & Tricks
SQL Server 2005
SQL Server 2008
SQL Server 2012
FAQ
Forums
Practice Test
Bookstore
Tip of the Day : How to Refresh Intellisense
Home > Tips & Tricks > Error Messages 501 to 1000
SQL Server Error Messages - Errors 501 to 1000

A message number uniquely identifies each error message and the error message text describes the problem.  The error message text often includes placeholders for information (such as object names) to be inserted in the error message when it is displayed.  Unfortunately, the error message text does not tell you how to solve or work around the problem.  In this series of Error Messages list, we will try to provide you with ways on how to overcome or work around certain error messages.

Some error messages are self-explanatory and can easily be fixed, such as "Invalid object name".  Others are harder to fix or work around, especially by those who are new to SQL Server.  It is the intent of this page and succeeding pages (to come) to assist you in addressing or working around SQL Server error messages.

Error Severity Description
502 16 The SQL Debugging Interface (SDI) requires that SQL Server, when started as a service, must not log on as System Account. Reset to log on as user account using Control Panel.
503 16 Unable to send symbol information to debugger on %ls for connection %d. Debugging disabled.
504 16 Unable to connect to debugger on %ls (Error = 0x%08x). Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered on %.*ls. Debugging disabled for connection %d.
505 16 The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed.
506 16 The invalid escape character "%.*ls" was specified in a %ls predicate.
507 16 Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer.
508 16 Unable to connect to debugger on %ls (Error = 0x%08x). Ensure that client-side components, such as SQLLE.DLL, are installed and registered on %.*ls. Debugging disabled for connection %d.
509 11 User name '%.*ls' not found.
510 16 Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint.
511 16 Cannot create a row of size %d which is greater than the allowable maximum of %d.
512 16 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
513 16 A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database '%.*ls', table '%.*ls', column '%.*ls'.
514 16 Unable to communicate with debugger on %ls (Error = 0x%08x). Debugging disabled for connection %d.
515 16 Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails.
516 16 Attempt to initialize OLE library failed. Check for correct versions of OLE DLLs on this machine.
517 16 Adding a value to a '%ls' column caused overflow.
518 16 Cannot convert data type %ls to %ls.
520 16 SQL Server no longer supports version %d of the SQL Debugging Interface (SDI).
522 16 The WAITFOR thread was evicted.
523 16 A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active.
524 16 A trigger returned a resultset and the server option 'disallow results from triggers' is true.
525 16 The column that was returned from the nodes() method cannot be converted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.
526 16 %ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query.
527 16 Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query.
528 16 System error detected during attempt to use the 'upsleep' system function.
529 16 Explicit conversion from data type %ls to %ls is not allowed.
530 16 The statement terminated. The maximum recursion %d has been exhausted before statement completion.
531 10 Cannot set NOCOUNT to OFF inside the trigger execution because the server option "disallow_results_from_triggers" is true or we are inside LOGON trigger execution.
532 16 The timestamp (changed to %S_TS) shows that the row has been updated by another user.
533 10 Cannot set XACT ABORT to OFF inside the trigger execution unless the database compatibility is 90.
534 16 '%.*ls' failed because it is not supported in the edition of this SQL Server instance '%.*ls'. See books online for more details on feature support in different SQL Server editions.
535 16
Difference of two datetime columns caused overflow at runtime.
The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.
536 16 Invalid length parameter passed to the substring function.
537 16 Invalid length parameter passed to the LEFT or SUBSTRING function.
538 16 Cannot find '%.*ls'. This language may have been dropped. Contact your system administrator.
539 16 Schema changed after the target table was created. Rerun the Select Into query.
540 16 There is insufficient system memory to run RAISERROR.
541 16 There is not enough stack to execute the statement
542 16 An invalid datetime value was encountered. Value exceeds the year 9999.
543 16 Creation of a return table failed for the table valued function '%.*ls'.
544 16 Cannot insert explicit value for identity column in table '<Table Name>' when IDENTITY_INSERT is set to OFF.
545 16 Explicit value must be specified for identity column in table '<Table Name>' when IDENTITY_INSERT is set to ON.
547 16 INSERT statement conflicted with COLUMN FOREIGN KEY constraint '%.*ls'. The conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls.
UPDATE statement conflicted with COLUMN REFERENCE constraint '%.*ls'. The conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls.
DELETE statement conflicted with COLUMN REFERENCE constraint '%.*ls'. The conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls.
548 16 The identity range managed by replication is full and must be updated by a replication agent. The %ls conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls. Sp_adjustpublisheridentityrange can be called to get a new identity range.
549 16 The collation '%.*ls' of receiving variable is not equal to the collation '%.*ls' of column '%.*ls'.
550 16 The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint.
551 16 The checksum has changed to %d. This shows that the row has been updated by another user.
552 16 CryptoAPI function "%ls" failed. Error 0x%x: %ls
555 16 User-defined functions are not yet enabled.
556 16 INSERT EXEC failed because the stored procedure altered the schema of the target table.
557 16 Only functions and extended stored procedures can be executed from within a function.
558 16 Remote function calls are not allowed within a function.
561 16 Failed to access file '%.*ls'
562 16 Failed to access file '%.*ls'. Files can be accessed only through shares
563 14 The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated.
564 16 Attempted to create a record with a fixed length of '%d'. Maximum allowable fixed length is '%d'.
565 18 The server encountered a stack overflow during compile time.
566 21 Error writing audit trace. SQL Server is shutting down.
567 16 File '%.*ls' either does not exist or is not a recognizable trace file. Or there was an error opening the file.
568 16 Server encountered an error '%.*ls'.
569 16 The handle that was passed to %ls was invalid.
570 15 INSTEAD OF triggers do not support direct recursion. The trigger execution failed.
571 16 The specified attribute value for %ls is invalid.
572 16 Invalid regular expression "%.*ls" near the offset %d.
573 16 Evaluation of the regular expression is too complex: '%.*ls'.
574 16 %ls statement cannot be used inside a user transaction.
575 16 A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets.
576 16 Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d.
577 16 The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647.
578 16 Insert Exec not allowed in WAITFOR queries.
579 16 Can not execute WAITFOR query with snapshot isolation level.
582 16 Offset is greater than the length of the column to be updated in write.
583 16 Negative offset or length in write.
584 16 Select Into not allowed in WAITFOR queries.
585 16 Changing database context is not allowed when populating the resource database.
587 16 An invalid delayed CLR type fetch token is provided.
588 16 Multiple tasks within the session are using the same delayed CLR type fetch token at the same time.
589 16 This statement has attempted to access data whose access is restricted by the assembly.
590 16 RPC was aborted without execution.
591 16 %ls: The formal parameter "%ls" was defined as OUTPUT, but the actual parameter was not declared as OUTPUT.
592 16 Cannot find %S_MSG ID %d in database ID %d.
593 10 fn_trace_gettable: XML conversion of trace data for event 165 failed.
594 10 fn_trace_gettable: XML conversion of trace data is not supported in fiber mode.
595 16 Bulk Insert with another outstanding result set should be run with XACT_ABORT on.
596 16 Cannot continue the execution because the session is in the kill state.
597 16 The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP).
598 16 An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information.
599 16 %.*ls: The length of the result exceeds the length limit (2GB) of the target large type.
601 12 Could not continue scan with NOLOCK due to data movement.
602 21 Could not find row in sysindexes for database ID %d, object ID %ld, index ID %d. Run DBCC CHECKTABLE on sysindexes.
603 21 Could not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHE
604 21 Could not find row in sysobjects for object ID %ld in database '%.*ls'. Run DBCC CHECKTABLE on sysobjects.
605 21 Attempt to fetch logical page %S_PGID in database '%.*ls' belongs to object '%.*ls', not to object '%.*ls'.
606 21 Metadata inconsistency. Filegroup id %ld specified for table '%.*ls' does not exist. Run DBCC CHECKDB or CHECKCATALOG.
607 21 Insufficient room was allocated for search arguments in the session descriptor for object '%.*ls'. Only %d search arguments were anticipated.
608 16 No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.
609 16 BTree is not empty when waking up on RowsetBulk.
610 16 Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption.
611 16 Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit.
613 21 Could not find an entry for worktable rowset with partition ID %I64d in database %d.
615 21 Could not find database table ID %d, name '%.*ls'.
617 20 Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it.
618 21 A varno of %d was passed to the opentable system function. The largest valid value is %d.
622 16 Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and text, ntext, and image columns cannot be populated on this filegroup until a file is added.
623 21 Could not retrieve row from page by RID because logical page %S_PGID is not a data page. %S_RID. %S_PAGE.
624 21 Could not retrieve row from page by RID because the requested RID has a higher number than the last RID on the page. %S_RID.%S_PAGE, DBID %d.
625 21 Cannot retrieve row from page %S_PGID by RID because the slotid (%d) is not valid.
626 16 Cannot use ROLLBACK with a savepoint within a distributed transaction.
627 16 Cannot use SAVE TRANSACTION within a distributed transaction.
628 13 Cannot issue SAVE TRANSACTION when there is no active transaction.
635 20 Process %d tried to remove DES resource lock %S_DES, which it does not hold.
637 20 Index shrink program returned invalid status of 0.
639 21 Could not fetch logical page %S_PGID, database ID %d. The page is not currently allocated.
644 21 Could not find the index entry for RID '%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'.
649 21 Could not find the clustered index entry for page %S_PGID, object ID %ld, status 0x%x. Index page %S_PGID, in database '%.*ls', was searched for this entry.
650 16 You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.
651 16 Cannot use %hs granularity hint on table '%.*ls' because locking at the specified granularity is inhibited.
652 16 Index ID %d for table '%.*ls' resides on a read-only filegroup which cannot be modified.
653 20 Two buffers are conflicting for the same keep slot in table '%.*ls'.
654 20 No slots are free to keep buffers for table '%.*ls'.
655 20 Expected to find buffer in keep slot for table '%.*ls'.
656 10 The partitioning function '%.*ls' creates %d partitions, which prevents removal of increased partitions support.
657 16 Could not disable support for increased partitions in database '%.*ls' because %S_MSG.
658 16 Could not enable support for increased partitions in database '%.*ls' because %S_MSG.
666 16 Maximum system-generated unique value for a duplicate group exceeded for table ID %d, index ID %d. Dropping and re-creating the index may fix the problem; otherwise use another clustering key.
667 16 Index %d for table '%.*ls' resides on offline filegroup that cannot be accessed.
669 22 The row object is inconsistent. Please rerun the query.
670 16 Large object (LOB) data for table "%.*ls" resides on an offline filegroup ("%.*ls") that cannot be accessed.
671 16 Large object (LOB) data for table "%.*ls" resides on a read-only filegroup ("%.*ls"), which cannot be modified.
672 10 Failed to queue cleanup packets for orphaned rowsets in database "%.*ls". Some disk space may be wasted. Cleanup will be attempted again on database restart.
674 10 Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem.
675 10 Worktable with partition ID %I64d was dropped successfully after repeated attempts.
676 10 Error occurred while attempting to drop worktable with partition ID %I64d.
677 10 Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.
678 10 Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process id
679 16 One of the partitions of index '%.*ls' for table '%.*ls'(partition ID %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result.
680 10 Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d.
681 16 Attempting to set a non-NULL-able column's value to NULL.
682 16 Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.
683 22 An internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption.
684 22 An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption.
685 22 An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.

Error Severity Description
701 19 There is insufficient system memory to run this query.
708 10 Warning: Due to low virtual memory, special reserved memory used %d times since startup. Increase virtual memory on server.
801 20 A buffer was encountered with an unexpected status of 0x%x.
802 17 No more buffers can be stolen.
803 10 simulated failure (DEBUG only)
804 20 Could not find buffer 0x%lx holding logical page %S_PGID in the SDES 0x%lx kept buffer pool for object '%.*ls'.
805 10 restore pending
806 10 audit failure (a page read from disk failed to pass basic integrity checks)
807 10 (no disk or the wrong disk is in the drive)
808 10 insufficient bytes transferred
809 20 Buffer 0x%lx, allocation page %S_PGID, in database '%.*ls' is not in allocation buffer pool in PSS (process status structure). Contact Technical Support.
813 20 Logical page %S_PGID in database ID %d is already hashed.
816 20 Process ID %d tried to remove a buffer resource lock %S_BUF that it does not hold in SDES %S_SDES. Contact Technical Support.
818 19 There is no room to hold the buffer resource lock %S_BUF in SDES %S_SDES. Contact Technical Support.
821 20 Could not unhash buffer at 0x%lx with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE.
822 21 Could not start I/O for request %S_BLKIOPTR.
823 24 I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.
824 24 SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log or system event log may provide more detail.
825 10 A read of the file '%ls' at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be co
826 10 incorrect pageid (expected %d:%d; actual %d:%d)
829 21 Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
830 10 stale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u))
831 20 Unable to deallocate a kept page.
832 24 A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file '%ls', page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption.
833 10 SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database [%ls] (%d). The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x
834 21 The bufclean system function was called on dirty buffer (page %S_PGID, stat %#x/%#x, objid %#x, sstat%#x).
840 17 Device '%.*ls' (physical name '%.*ls', virtual device number %d) is not available. Contact the system administrator for assistance.
844 10 Time out occurred while waiting for buffer latch type %d, bp %#x, page %S_PGID, stat %#x, object ID %d:%d:%d, waittime %d. Continuing to wait.
845 17 Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
846 10 A time-out occurred while waiting for buffer latch -- type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Not continuing to wait.
847 10 Timeout occurred while waiting for latch: class '%ls', id %p, type %d, Task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Continuing to wait.
848 10 Using large pages for buffer pool.
849 10 Using locked pages for buffer pool.
850 10 %I64u MB of large page memory allocated.
851 10 the page is in an OFFLINE file which cannot be read
901 21 Could not find descriptor for database ID %d, object ID %ld in hash table after hashing it.
902 16 To change the %ls, the database must be in state in which a checkpoint can be executed.
903 22 Could not find row in sysindexes for clustered index on system catalog %ld in database ID %d. This index should exist in all databases. Run DBCC CHECKTABLE on sysindexes in the database.
904 16 Database %ld cannot be autostarted during server shutdown or startup.
905 21 Database '%.*ls' cannot be started in this edition of SQL Server because it contains a partition function '%.*ls'. Only Enterprise edition of SQL Server supports partitioning.
906 22 Could not locate row in sysobjects for system catalog '%.*ls' in database '%.*ls'. This system catalog should exist in all databases. Run DBCC CHECKTABLE on sysobjects in this database.
907 16 The database "%ls" has inconsistent database or file metadata.
908 10 Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available.
909 21 Database '%.*ls' cannot be started in this edition of SQL Server because part or all of object '%.*ls' is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterpris
910 10 Database '%.*ls' is upgrading script '%.*ls' from level %d to level %d.
911 16 Could not locate entry in sysdatabases for database '%.*ls'. No entry found with that name. Make sure that the name is entered correctly.
912 21 Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error
913 22 Could not find database ID %d. Database may not be activated yet or may be in transition.
914 21 Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' was aborted before completion. If the abort happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous
915 21 Unable to obtain the current script level for database '%.*ls'. If the error happened during startup of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the approp
916 14 Server user '%.*ls' is not a valid user in database '%.*ls'.
917 21 An upgrade script batch failed to execute for database '%.*ls' due to compilation error. Check the previous error message for the line which caused compilation to fail.
918 21 Failed to load the engine script metadata from script DLL '%.*ls'. The error code reported by Windows was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resol
919 10 User '%.*ls' is changing database script level entry %d to a value of %d.
920 20 Only members of the sysadmin role can modify the database script level.
921 14 Database '%.*ls' has not been recovered yet. Wait and try again.
922 14 Database '%.*ls' is being recovered. Waiting until recovery is finished.
923 14 Database '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it.
924 14 Database '%.*ls' is already open and can only have one user at a time.
925 19 Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.
926 14 Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
927 14 Database '%.*ls' cannot be opened. It is in the middle of a restore.
928 20 During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.
929 20 Attempting to close a database that is not already open. Contact Technical Support.
930 21 Attempting to reference recovery unit %d in database '%ls' which does not exist. Contact Technical Support.
931 21 Attempting to reference database fragment %d in database '%ls' which does not exist. Contact Technical Support.
932 21 SQL Server cannot load database '%.*ls' because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgra
933 21 Database '%.*ls' cannot be started because some of the database functionality is not available in the current edition of SQL Server.
934 21 SQL Server cannot load database '%.*ls' because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Serv
935 21 The script level for '%.*ls' in database '%.*ls' cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install
941 14 Cannot open database '%.*ls'. It has not been upgraded to the latest format.
942 14 Database '%.*ls' cannot be opened because it is offline.
943 14 Database '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d).
944 10 Converting database '%.*ls' from version %d to the current version %d.
945 16 Database '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
946 14 Cannot open database '%.*ls' version %d. Upgrade the database to the latest version.
947 16 Error while closing database '%.*ls' cleanly.
948 14 Database '%.*ls' cannot be upgraded. Database is version %d and this server supports version %d.
949 16 tempdb is skipped. You cannot run a query that requires tempdb
950 14 Database '%.*ls' cannot be upgraded - database has a version (%d) earlier than SQL Server 7.0(%d).
951 10 Database '%.*ls' running the upgrade step from version %d to version %d.
952 16 Database '%.*ls' is in transition. Try the statement later.
953 16 Warning: Index '%ls' on '%ls' in database '%ls' may be corrupt because of expression evaluation changes in this release. Drop and re-create the index.
954 14 The database "%.*ls" cannot be opened. It is acting as a mirror database.
955 14 Database %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the partner and witness connections if configured.
956 14 Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later.
957 17 Database '%.*ls' is enabled for Database Mirroring, The name of the database may not be changed.
958 10 The resource database build version is %.*ls. This is an informational message only. No user action is required.
959 20 The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server.
960 10 Warning: User "sys" (principal_id = %d) in database "%.*ls" has been renamed to "%.*ls". "sys" is a reserved user or schema name in this version of SQL Server.
961 10 Warning: Index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls" was renamed to "%.*ls" because its name is a duplicate of another index on the same object.
962 10 Warning: Primary key or Unique constraint "%.*ls" (object_id = %d) in database "%.*ls" was renamed to "%.*ls" because its index was renamed.
963 10 Warning: Database "%.*ls" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state.
964 10 Warning: System user '%.*ls' was found missing from database '%.*ls' and has been restored. This user is required for SQL Server operation.
965 10 Warning: A column nullability inconsistency was detected in the metadata of index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
966 10 Warning: Assembly "%.*ls" in database "%.*ls" has been renamed to "%.*ls" because the name of the assembly conflicts with a system assembly in this version of SQL Server.
967 10 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled because the XML data bound to it may contain negative values for xs:date and xs:dateTime which are not longer supported.
968 10 Warning: The XML facet on type "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.
969 10 Warning: The default or fixed value on XML element or attribute "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.
970 10 Warning: The XML instances in the XML column "%.*ls.%.*ls.%.*ls" may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary XML index on these XML instances.
971 10 The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' instead of the currently attached resource database at '%.*ls'.
972 17 Could not use database '%d' during procedure execution.
973 10 Database %ls was started . However, FILESTREAM is not compatible with the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION options. Either remove the FILESTREAM files and the FILESTREAM filegroups, or set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_

Related Articles :