SQL Server Errors or Failures from Error: 8995 to Error: 9015

SQLServerF1

 

Error: 8995, Severity: 16, System table ‘%.*ls’ (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d.
Error: 8996, Severity: 16, IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) controls pages in filegroup %d, that should be in filegroup %d.
Error: 8997, Severity: 16, Service Broker Msg %d, State %d: %.*ls
Error: 8998, Severity: 16, Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID %d pages from %S_PGID to %S_PGID. See other errors for cause.

Error: 8999, Severity: 10, Database tempdb allocation errors prevent further %ls processing.
Error: 9001, Severity: 21, The log for database ‘%.*ls’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Error: 9002, Severity: 17, The transaction log for database ‘%ls’ is full due to ‘%ls’.
Error: 9003, Severity: 20, The log scan number %S_LSN passed to log scan in database ‘%.*ls’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication.
Error: 9004, Severity: 21, An error occurred while processing the log for database ‘%.*ls’. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.

Error: 9005, Severity: 16, Either start LSN or end LSN specified in OpenRowset(DBLog, …) is invalid.
Error: 9006, Severity: 10, Cannot shrink log file %d (%s) because total number of logical log files cannot be fewer than %d.
Error: 9007, Severity: 10, Cannot shrink log file %d (%s) because requested size (%dKB) is larger than the start of the last logical log file.
Error: 9008, Severity: 10, Cannot shrink log file %d (%s) because the logical log file located at the end of the file is in use.
Error: 9009, Severity: 10, Cannot shrink log file %d (%s) because of minimum log space required.
Error: 9010, Severity: 14, User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission
Error: 9011, Severity: 14, User does not have permission to query backup files with the virtual table DBLog. Only members of the sysadmin fixed server role has this permission
Error: 9012, Severity: 10, There have been %d misaligned log IOs which required falling back to synchronous IO. The current IO is on file %ls.
Error: 9013, Severity: 10, The tail of the log for database %ls is being rewritten to match the new sector size of %d bytes. %d bytes at offset %I64d in file %ls will be written.
Error: 9014, Severity: 21, An error occurred while processing the log for database ‘%ls’. The log block version %d is unsupported. This server supports log version %d to %d.
Error: 9015, Severity: 24, The log record at LSN %S_LSN is corrupted.
This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 

SQL Server Errors or Failures from Error: 8975 to Error: 8994

SQLServerF1

 

Error: 8975, Severity: 10, DBCC cross-rowset check failed for object ‘%.*ls’ (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error.
Error: 8976, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors.
Error: 8977, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered.

Error: 8978, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem.
Error: 8979, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog.
Error: 8980, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered.
Error: 8981, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage.

Error: 8982, Severity: 16, Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) refers to page %S_PGID in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) but is not in the same index
Error: 8983, Severity: 10, File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.
Error: 8984, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d. A row should be on partition number %d but was found in partition number %d. Possible extra or invalid keys for:
Error: 8985, Severity: 16, Could not locate file ‘%.*ls’ for database ‘%.*ls’ in sys.database_files. The file either does not exist, or was dropped.
Error: 8986, Severity: 16, Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using “WITH ALL_ERRORMSGS”.
Error: 8987, Severity: 16, No help available for DBCC statement ‘%.*ls’.
Error: 8988, Severity: 16, Row (%d:%d:%d) identified by (%ls).
Error: 8989, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in database ‘%ls’.
Error: 8990, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
Error: 8991, Severity: 16, 0x%p to 0x%p is not a valid address range.
Error: 8992, Severity: 16, Check Catalog Msg %d, State %d: %.*ls
Error: 8993, Severity: 16, Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.
Error: 8994, Severity: 16, Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 

SQL Server Errors or Failures from Error: 8955 to Error: 8974

SQLServerF1

 

Error: 8955, Severity: 16, Data row (%d:%d:%d) identified by (%ls) with index values ‘%ls’.
Error: 8956, Severity: 16, Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls).
Error: 8957, Severity: 10, %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls
Error: 8958, Severity: 10, %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls).
Error: 8959, Severity: 16, Table error: IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID.

Error: 8960, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID, slot %d, column %d is not a valid complex column.
Error: 8961, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d.
Error: 8962, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has incorrect node type %d.
Error: 8963, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d.

Error: 8964, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is not referenced.
Error: 8965, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan.
Error: 8966, Severity: 22, Unable to read and latch page %S_PGID with latch type %ls. %ls failed.
Error: 8967, Severity: 16, An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
Error: 8968, Severity: 16, Table error: %ls page %S_PGID (object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls)) is out of the range of this database.
Error: 8969, Severity: 16, Table error: IAM chain linkage error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID.
Error: 8970, Severity: 16, Row error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID, row ID %d. Column ‘%.*ls’ was created NOT NULL, but is NULL in the row.
Error: 8971, Severity: 16, Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d
Error: 8972, Severity: 16, Forwarded row referenced by more than one row. Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, slot %d incorrectly points to the forwarded row page %S_PGID, slot %d, which correctly refers back to page %S_PGID, slot %d.
Error: 8973, Severity: 16, CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice.
Error: 8974, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 

SQL Server Errors or Failures from Error: 8935 to Error: 8954

SQLServerF1

 

Error: 8935, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page.
Error: 8936, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->Prev = %S_PGID.
Error: 8937, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d.

Error: 8938, Severity: 16, Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d.
Error: 8939, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Values are %ld and %ld.
Error: 8940, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Address 0x%x is not aligned.
Error: 8941, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x is invalid.
Error: 8942, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x overlaps with the prior row.

Error: 8943, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, row extends into free space at 0x%x.
Error: 8944, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page (%d:%d), row %d. Test (%.*ls) failed. Values are %ld and %ld.
Error: 8945, Severity: 16, Table error: Object ID %d, index ID %d will be rebuilt.
Error: 8946, Severity: 16, Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, alloc unit ID and page ID on the page.
Error: 8947, Severity: 16, Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID.
Error: 8948, Severity: 16, Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x.
Error: 8949, Severity: 10, %.*ls fixed %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
Error: 8950, Severity: 16, %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object.
Error: 8951, Severity: 16, Table error: table ‘%ls’ (ID %d). Data row does not have a matching index row in the index ‘%ls’ (ID %d). Possible missing or invalid keys for the index row matching:
Error: 8952, Severity: 16, Table error: table ‘%ls’ (ID %d). Index row in index ‘%ls’ (ID %d) does not match any data row. Possible extra or invalid keys for:
Error: 8953, Severity: 10, Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
Error: 8954, Severity: 10, %.*ls found %d allocation errors and %d consistency errors not associated with any single object.
This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 

SQL Server Errors or Failures from Error: 7948 to Error: 7969

SQLServerF1

 

Error: 7948, Severity: 10, – Avg. Pages per Extent……………………: %3.1f
Error: 7949, Severity: 10, – Scan Density [Best Count:Actual Count]…….: %4.2f%ls [%I64d:%I64d]
Error: 7950, Severity: 10, – Logical Scan Fragmentation ………………: %4.2f%ls
Error: 7951, Severity: 10, Warning: Could not complete filestream consistency checks due to an operating system error. Any consistency errors found in the filestream subsystem will be silenced. Please refer to other errors for more information. This condition is likely transien
Error: 7952, Severity: 10, – Extent Scan Fragmentation ……………….: %4.2f%ls

Error: 7953, Severity: 10, – Avg. Bytes Free per Page…………………: %3.1f
Error: 7954, Severity: 10, – Avg. Page Density (full)…………………: %4.2f%ls
Error: 7955, Severity: 16, Invalid SPID %d specified.
Error: 7956, Severity: 16, Table error: The FILESTREAM file “%.*ls” for column ID %d was found in column directory ID %.*ls of container ID %d but should be in container ID %d in object ID %d, index ID %d, partition ID %I64d, page ID %S_PGID, slot ID %d.
Error: 7957, Severity: 10, Cannot display the specified SPID’s buffer; in transition.
Error: 7958, Severity: 16, The specified SPID does not process input/output data streams.
Error: 7960, Severity: 16, An invalid server process identifier (SPID) %d or batch ID %d was specified.

Error: 7961, Severity: 16, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) , page ID %S_PGID, row ID %d. Column ‘%.*ls’ is a var column with a NULL value and non-zero data length
Error: 7962, Severity: 16, Invalid BATCHID %d specified.
Error: 7963, Severity: 16, Database error: The file “%.*ls” is not a valid FILESTREAM LOG file in container ID %d.
Error: 7964, Severity: 10, Repair: Deleted FILESTREAM file “%.*ls” for column ID %d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
Error: 7965, Severity: 16, Table error: Could not check object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) due to invalid allocation (IAM) page(s).
Error: 7966, Severity: 10, Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped.
Error: 7968, Severity: 10, Transaction information for database ‘%.*ls’.
Error: 7969, Severity: 16, No active open transactions.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 

SQL Server Errors or Failures from Error: 7927 to Error: 7947

SQLServerF1

 

Error: 7927, Severity: 10, Total number of extents is %I64d.
Error: 7928, Severity: 16, The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
Error: 7929, Severity: 16, Check statement aborted. Database contains deferred transactions.
Error: 7930, Severity: 16, Mirroring must be removed from the database for this DBCC command.

Error: 7931, Severity: 16, Database error: The FILESTREAM directory ID %.*ls for a partition was seen two times.
Error: 7932, Severity: 16, Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d is in filegroup %d, but should be in filegroup %d.
Error: 7933, Severity: 16, Table error: A FILESTREAM directory ID %.*ls exists for a partition, but the corresponding partition does not exist in the database.
Error: 7934, Severity: 16, DBCC CHECK cannot proceed on database %.*ls because it is a Secondary Replica and either Snapshot creation failed or the WITH TABLOCK option was specified. Secondary Replica databases cannot be exclusively locked for DBCC CHECK. Reason may have been given
Error: 7935, Severity: 16, Table error: A FILESTREAM directory ID %.*ls exists for a column of object ID %d, index ID %d, partition ID %I64d, but that column does not exist in the partition.

Error: 7936, Severity: 16, Table error: The FILESTREAM directory ID %.*ls exists for column ID %d of object ID %d, index ID %d, partition ID %I64d, but that column is not a FILESTREAM column.
Error: 7938, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name “%.*ls” twice in the column directory %d container ID %d (for column ID %d).
Error: 7939, Severity: 16, Cannot detach database ‘%.*ls’ because it does not exist.
Error: 7940, Severity: 16, System databases master, model, msdb, and tempdb cannot be detached.
Error: 7941, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name “%.*ls” twice in the column ID %d (for column directory %d container ID %d).
Error: 7942, Severity: 10, DBCC %ls scanning ‘%.*ls’ table…
Error: 7943, Severity: 10, Table: ‘%.*ls’ (%d); index ID: %d, database ID: %d
Error: 7944, Severity: 10, %ls level scan performed.
Error: 7945, Severity: 10, – Pages Scanned…………………………..: %I64d
Error: 7946, Severity: 10, – Extents Scanned…………………………: %I64d
Error: 7947, Severity: 10, – Extent Switches…………………………: %I64d

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 

SQL Server Errors or Failures from Error: 7907 to Error: 7926

SQLServerF1

 

Error: 7907, Severity: 16, Table error: The directory “%.*ls” under the rowset directory ID %.*ls is not a valid FILESTREAM directory in container ID %d.
Error: 7908, Severity: 16, Table error: The file “%.*ls” in the rowset directory ID %.*ls is not a valid FILESTREAM file in container ID %d.
Error: 7909, Severity: 20, The emergency-mode repair failed.You must restore from backup.
Error: 7910, Severity: 10, Repair: The page %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7911, Severity: 10, Repair: The page %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7912, Severity: 10, Repair: The extent %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).

Error: 7913, Severity: 10, Repair: The extent %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7914, Severity: 10, Repair: %ls page at %S_PGID has been rebuilt.
Error: 7915, Severity: 10, Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt.
Error: 7916, Severity: 10, Repair: Deleted record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), on page %S_PGID, slot %d. Indexes will be rebuilt.
Error: 7917, Severity: 10, Repair: Converted forwarded record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), at page %S_PGID, slot %d to a data row.

Error: 7918, Severity: 10, Repair: Page %S_PGID next and %S_PGID previous pointers have been set to match each other in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7919, Severity: 16, Repair statement not processed. Database needs to be in single user mode.
Error: 7920, Severity: 10, Processed %ld entries in system catalog for database ID %d.
Error: 7921, Severity: 16, Repair statement not processed. Database cannot be a snapshot.
Error: 7922, Severity: 16, ***************************************************************
Error: 7923, Severity: 10, Table %.*ls Object ID %ld.
Error: 7924, Severity: 10, Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). FirstIAM %S_PGID. Root %S_PGID. Dpages %I64d.
Error: 7925, Severity: 10, Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). %I64d pages used in %I64d dedicated extents.
Error: 7926, Severity: 16, Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previ

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 
1 2