Severity: 10
Description: DBCC %ls scanning '%.*ls' table...
Possibly related links:
Errors 7000 - 7999
OLE DB provider '%ls' does not contain table '%ls' ... Use 'DBCC TRACEON()'. 7942. 10. DBCC %ls scanning '%.*ls' table... 7943. 10 ...
OLE DB provider '%ls' does not contain table '%ls' ... Use 'DBCC TRACEON()'. 7942. 10. DBCC %ls scanning '%.*ls' table... 7943. 10 ...
Errors 8000 - 8999
The current user is not the database or object owner of table '%.*ls' ... ls is the minimum repair level for the errors found by DBCC %ls (%ls %ls). 8959. 16 ...
The current user is not the database or object owner of table '%.*ls' ... ls is the minimum repair level for the errors found by DBCC %ls (%ls %ls). 8959. 16 ...
Errors 7000 - 7999
... qualified table names (schema or catalog) with the OLE DB provider "%ls" for ... DBCC %ls scanning '%.*ls' table... 7943. 10. No ...
... qualified table names (schema or catalog) with the OLE DB provider "%ls" for ... DBCC %ls scanning '%.*ls' table... 7943. 10. No ...
Errors 2000 - 2999
DBCC UPDATEUSAGE: sysindexes row updated for table '%.*ls' (index ID %ld): 2542. 10 ... of IAM page %S_PGID object ID %d index ID %d but was not detected in the scan. ...
DBCC UPDATEUSAGE: sysindexes row updated for table '%.*ls' (index ID %ld): 2542. 10 ... of IAM page %S_PGID object ID %d index ID %d but was not detected in the scan. ...
Errors 8000 - 8999
Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X ... If no clean backup is available, consider running DBCC CHECKDB. ...
Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X ... If no clean backup is available, consider running DBCC CHECKDB. ...
Errors 9000 - 9999
If no clean backup is available, consider running DBCC CHECKDB. ... text %ls population initialized for table or indexed view '%ls' (table or ...
If no clean backup is available, consider running DBCC CHECKDB. ... text %ls population initialized for table or indexed view '%ls' (table or ...
Errors 3000 - 3999
The DBCC RECOVERDB statement can only be run after a RESTORE ... Table '%.*ls'. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d. ...
The DBCC RECOVERDB statement can only be run after a RESTORE ... Table '%.*ls'. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d. ...
SQL Server 2005 Row Versioning-Based Transaction Isolation
You publish only the table you require, and you can apply row filters and column ... to update is done by using a blocking scan where an update lock is taken on the ...
You publish only the table you require, and you can apply row filters and column ... to update is done by using a blocking scan where an update lock is taken on the ...
SQL Server 2005 Row Versioning-Based Transaction Isolation
You publish only the table you require, and you can apply row filters and column ... to update is done by using a blocking scan where an update lock is taken on the ...
You publish only the table you require, and you can apply row filters and column ... to update is done by using a blocking scan where an update lock is taken on the ...
Errors 10000 - 10999
... ls" because it uses non-deterministic common language runtime (CLR) table-valued ... consistency of master database by running DBCC CHECKCATALOG('master' ...
... ls" because it uses non-deterministic common language runtime (CLR) table-valued ... consistency of master database by running DBCC CHECKCATALOG('master' ...
User suggestions:
There are no user suggestions approved yet. Use the comments section to be the first!
There are no user suggestions approved yet. Use the comments section to be the first!
Няма коментари:
Публикуване на коментар