July 15, 2016 at 11:15 pm
Hi,
I had one of my DB has some corruption. Looks like, need to restore from backup. I have a good backup and planning to restore same server as well as other server and will try to run the checkdb again.
Do have any other suggestions.
It looks like same as my case --> http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=90926
SQL Server 2012 - 11.0.5058.0
==============
dbcc checkdb ('DB') with no_infomsgs,all_errormsgs
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5782993) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5782994) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594055688192 (type LOB data), page (1:5782992). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594055688192 (type LOB data): Page (1:5782992) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594055688192 (type LOB data): Page (1:5782993) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594055688192 (type LOB data): Page (1:5782994) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594055688192 (type LOB data). The off-row data node at page (1:5782992), slot 0, text ID 912195584 is referenced by page (1:5782938), slot 0, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594055688192 (type LOB data). The off-row data node at page (1:5782993), slot 0, text ID 912195584 is referenced by page (1:5782938), slot 0, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594055688192 (type LOB data). The off-row data node at page (1:5782994), slot 0, text ID 912195584 is referenced by page (1:5782938), slot 0, but was not seen in the scan.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8534654:4)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8534716:27)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8536618:83)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8539814:54)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8540209:23)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8540400:38)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8540693:32)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8542715:22)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8543775:32)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8543912:44)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8543946:25)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8545605:31)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8547125:51)
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594166575104, alloc unit ID 72057594192855040 (type In-row data):
Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8547276:27)
CHECKDB found 0 allocation errors and 21 consistency errors in table 'Table' (object ID 926626344).
CHECKDB found 0 allocation errors and 23 consistency errors in database 'DB'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB ().
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
July 16, 2016 at 8:47 am
Restore should (almost) always be your first choice, so if you have good backups and can restore, do so.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 17, 2016 at 11:44 pm
Have a look at this link
http://dba.stackexchange.com/questions/88982/how-to-repair-database-consistency-errors
July 18, 2016 at 12:19 am
Thanks Gail. Unfortunately, The last full backup also corrupted. Bad that, we do not have checkDB weekly once, Since checkDB runs more than 24 hours..
I just restored the last full backup another server and got the same error and run the repair_allow_data_loss and the table repaired and the count(*) of table more or less same.
I have asked the team to take old backup from tape to server, will take some time. Once, it's done i am going to run checkDB and see that works or not. If it worked, which will be good. I mean take a table from good restored DB and re import to production DB and drop the table (OR) repair_arun llow_data_loss production and match the table.
============
DBCC results for 'Backup_of_DB'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5782993) contains an incorrect page ID in its page header.
The PageId in the page header = (0:0).
The error has been repaired.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5782994) contains an incorrect page ID in its page header.
The PageId in the page header = (0:0).
The error has been repaired.
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
CHECKDB fixed 0 allocation errors and 2 consistency errors not associated with any single object.
DBCC results for 'sys.sysrscols'.
There are 7111 rows in 80 pages for object "sys.sysrscols".
DBCC results for 'sys.sysrowsets'.
There are 409 rows in 4 pages for object "sys.sysrowsets".
DBCC results for 'sys.sysclones'.
There are 0 rows in 0 pages for object "sys.sysclones".
DBCC results for 'sys.sysallocunits'.
There are 507 rows in 9 pages for object "sys.sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.sysseobjvalues'.
There are 0 rows in 0 pages for object "sys.sysseobjvalues".
DBCC results for 'sys.syspriorities'.
There are 0 rows in 0 pages for object "sys.syspriorities".
DBCC results for 'sys.sysdbfrag'.
There are 0 rows in 0 pages for object "sys.sysdbfrag".
DBCC results for 'sys.sysfgfrag'.
There are 0 rows in 0 pages for object "sys.sysfgfrag".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.syspru'.
There are 0 rows in 0 pages for object "sys.syspru".
DBCC results for 'sys.sysbrickfiles'.
There are 0 rows in 0 pages for object "sys.sysbrickfiles".
DBCC results for 'sys.sysphfg'.
There are 1 rows in 1 pages for object "sys.sysphfg".
DBCC results for 'sys.sysprufiles'.
There are 2 rows in 1 pages for object "sys.sysprufiles".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysowners'.
There are 19 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysdbreg'.
There are 0 rows in 0 pages for object "sys.sysdbreg".
DBCC results for 'sys.sysprivs'.
There are 4987 rows in 37 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 4609 rows in 85 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 39477 rows in 796 pages for object "sys.syscolpars".
DBCC results for 'sys.sysxlgns'.
There are 0 rows in 0 pages for object "sys.sysxlgns".
DBCC results for 'sys.sysxsrvs'.
There are 0 rows in 0 pages for object "sys.sysxsrvs".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.sysusermsgs'.
There are 0 rows in 0 pages for object "sys.sysusermsgs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysrmtlgns'.
There are 0 rows in 0 pages for object "sys.sysrmtlgns".
DBCC results for 'sys.syslnklgns'.
There are 0 rows in 0 pages for object "sys.syslnklgns".
DBCC results for 'sys.sysxprops'.
There are 0 rows in 0 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 59 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 1156 rows in 31 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 2024 rows in 14 pages for object "sys.sysiscols".
DBCC results for 'sys.sysendpts'.
There are 0 rows in 0 pages for object "sys.sysendpts".
DBCC results for 'sys.syswebmethods'.
There are 0 rows in 0 pages for object "sys.syswebmethods".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysaudacts'.
There are 0 rows in 0 pages for object "sys.sysaudacts".
DBCC results for 'sys.sysobjvalues'.
There are 3371 rows in 621 pages for object "sys.sysobjvalues".
DBCC results for 'sys.syscscolsegments'.
There are 0 rows in 0 pages for object "sys.syscscolsegments".
DBCC results for 'sys.syscsdictionaries'.
There are 0 rows in 0 pages for object "sys.syscsdictionaries".
DBCC results for 'sys.sysclsobjs'.
There are 19 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 284 rows in 2 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 31478 rows in 261 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysfoqueues'.
There are 0 rows in 0 pages for object "sys.sysfoqueues".
DBCC results for 'sys.syschildinsts'.
There are 0 rows in 0 pages for object "sys.syschildinsts".
DBCC results for 'sys.syscompfragments'.
There are 0 rows in 0 pages for object "sys.syscompfragments".
DBCC results for 'sys.sysftsemanticsdb'.
There are 0 rows in 0 pages for object "sys.sysftsemanticsdb".
DBCC results for 'sys.sysftstops'.
There are 0 rows in 0 pages for object "sys.sysftstops".
DBCC results for 'sys.sysftproperties'.
There are 0 rows in 0 pages for object "sys.sysftproperties".
DBCC results for 'sys.sysxmitbody'.
There are 0 rows in 0 pages for object "sys.sysxmitbody".
DBCC results for 'sys.sysfos'.
There are 0 rows in 0 pages for object "sys.sysfos".
DBCC results for 'sys.sysqnames'.
There are 98 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 100 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 112 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 19 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 3 rows in 1 pages for object "sys.sysbinsubobjs".
DBCC results for 'sys.syssoftobjrefs'.
There are 7017 rows in 106 pages for object "sys.syssoftobjrefs".
DBCC results for 'NameValuePair_Hebrew_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hebrew_CI_AS".
DBCC results for 'NameValuePair_Hindi_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hindi_CI_AS".
DBCC results for 'WebsPlus'.
There are 106 rows in 2 pages for object "WebsPlus".
DBCC results for 'NameValuePair_Hungarian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hungarian_CI_AS".
DBCC results for 'NameValuePair_Hungarian_Technical_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hungarian_Technical_CI_AS".
DBCC results for 'SiteQuota'.
There are 0 rows in 1 pages for object "SiteQuota".
DBCC results for 'NameValuePair_Icelandic_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Icelandic_CI_AS".
DBCC results for 'NameValuePair_Japanese_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Japanese_CI_AS".
DBCC results for 'AllSites'.
There are 15 rows in 2 pages for object "AllSites".
DBCC results for 'NameValuePair_Japanese_Unicode_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Japanese_Unicode_CI_AS".
DBCC results for 'NameValuePair_Korean_Wansung_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Korean_Wansung_CI_AS".
DBCC results for 'Versions'.
There are 6 rows in 1 pages for object "Versions".
DBCC results for 'NameValuePair_Korean_Wansung_Unicode_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Korean_Wansung_Unicode_CI_AS".
DBCC results for 'NameValuePair_Latin1_General_CI_AS'.
There are 72 rows in 2 pages for object "NameValuePair_Latin1_General_CI_AS".
DBCC results for 'NameValuePair_Latvian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Latvian_CI_AS".
DBCC results for 'NameValuePair_Lithuanian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Lithuanian_CI_AS".
DBCC results for 'NameValuePair_Lithuanian_Classic_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Lithuanian_Classic_CI_AS".
DBCC results for 'NameValuePair_Traditional_Spanish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Traditional_Spanish_CI_AS".
DBCC results for 'NameValuePair_Modern_Spanish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Modern_Spanish_CI_AS".
DBCC results for 'NameValuePair_Polish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Polish_CI_AS".
DBCC results for 'NameValuePair_Romanian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Romanian_CI_AS".
DBCC results for 'NameValuePair_Slovak_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Slovak_CI_AS".
DBCC results for 'NameValuePair_Slovenian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Slovenian_CI_AS".
DBCC results for 'NameValuePair_Thai_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Thai_CI_AS".
DBCC results for 'AllDocs'.
There are 56191 rows in 3741 pages for object "AllDocs".
DBCC results for 'StorageMetrics'.
There are 55775 rows in 425 pages for object "StorageMetrics".
DBCC results for 'NameValuePair_Turkish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Turkish_CI_AS".
DBCC results for 'StorageMetricsChanges'.
There are 6214 rows in 47 pages for object "StorageMetricsChanges".
DBCC results for 'AllWebs'.
There are 106 rows in 100 pages for object "AllWebs".
DBCC results for 'NameValuePair_Ukrainian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Ukrainian_CI_AS".
DBCC results for 'NameValuePair_Vietnamese_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Vietnamese_CI_AS".
DBCC results for 'NameValuePair_Azeri_Cyrillic_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Azeri_Cyrillic_90_CI_AS".
DBCC results for 'NameValuePair_Azeri_Latin_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Azeri_Latin_90_CI_AS".
DBCC results for 'NameValuePair_Chinese_Hong_Kong_Stroke_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_Hong_Kong_Stroke_90_CI_AS".
DBCC results for 'NameValuePair_Divehi_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Divehi_90_CI_AS".
DBCC results for 'AllDocVersions'.
There are 11967 rows in 1940 pages for object "AllDocVersions".
DBCC results for 'NameValuePair_Indic_General_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Indic_General_90_CI_AS".
DBCC results for 'AllUserData'.
There are 49698 rows in 3613 pages for object "AllUserData".
DBCC results for 'NameValuePair_Kazakh_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Kazakh_90_CI_AS".
DBCC results for 'DocsToStreams'.
There are 593815 rows in 5047 pages for object "DocsToStreams".
DBCC results for 'DocStreams'.
Repair: The Clustered index successfully rebuilt for the object "dbo.DocStreams" in database "Backup_of_DB".
Repair: The page (1:5782992) has been deallocated from object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data).
Repair: The page (1:5782993) has been deallocated from object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data).
Repair: The page (1:5782994) has been deallocated from object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data).
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:670827), slot 4. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:670827), slot 4.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:673401), slot 27. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:673401), slot 27.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:971985), slot 19. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:971985), slot 19.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:2985907), slot 50. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:2985907), slot 50.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:3166199), slot 24. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:3166199), slot 24.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:3382909), slot 38. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:3382909), slot 38.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:3569951), slot 32. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:3569951), slot 32.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:5754265), slot 12. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:5754265), slot 12.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:6448708), slot 63. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:6448708), slot 63.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:6464660), slot 49. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:6464660), slot 49.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:6503121), slot 25. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:6503121), slot 25.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:7206584), slot 56. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:7206584), slot 56.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:8108162), slot 68. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:8108162), slot 68.
Repair: Deleted record for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data), on page (1:8159167), slot 28. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 912195584, for object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data) on page (1:8159167), slot 28.
Repair: The Nonclustered index successfully rebuilt for the object "dbo.DocStreams, DocStreams_RbsId" in database "Backup_of_DB".
Repair: The Nonclustered index successfully rebuilt for the object "dbo.DocStreams, DocStreams_Expiration" in database "Backup_of_DB".
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 1 will be rebuilt.
The error has been repaired.
Msg 8928, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data): Page (1:5782992) could not be processed. See other errors for details.
The error has been repaired.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data), page (1:5782992). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
The error has been repaired.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data). The off-row data node at page (1:5782992), slot 0, text ID 912195584 is referenced by page (1:5782938), slot 0, but was not seen in the scan.
The error has been repaired.
Msg 8928, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data): Page (1:5782993) could not be processed. See other errors for details.
The error has been repaired.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data). The off-row data node at page (1:5782993), slot 0, text ID 912195584 is referenced by page (1:5782938), slot 0, but was not seen in the scan.
The error has been repaired.
Msg 8928, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data): Page (1:5782994) could not be processed. See other errors for details.
The error has been repaired.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594055688192 (type LOB data). The off-row data node at page (1:5782994), slot 0, text ID 912195584 is referenced by page (1:5782938), slot 0, but was not seen in the scan.
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:670827:4)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:673401:27)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:971985:19)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:2985907:50)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:3166199:24)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:3382909:38)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:3569951:32)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:5754265:12)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:6448708:63)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:6464660:49)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:6503121:25)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:7206584:56)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8108162:68)
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 926626344, index ID 1, partition ID 72057594101760000, alloc unit ID 72057594123583488 (type In-row data): Errors found in off-row data with ID 912195584 owned by data record identified by RID = (1:8159167:28)
The error has been repaired.
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 2 will be rebuilt.
The error has been repaired.
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3 will be rebuilt.
The error has been repaired.
There are 485846 rows in 15993 pages for object "DocStreams".
CHECKDB found 0 allocation errors and 21 consistency errors in table 'DocStreams' (object ID 926626344).
CHECKDB fixed 0 allocation errors and 21 consistency errors in table 'DocStreams' (object ID 926626344).
DBCC results for 'NameValuePair_Macedonian_FYROM_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Macedonian_FYROM_90_CI_AS".
DBCC results for 'RecycleBin'.
There are 133 rows in 8 pages for object "RecycleBin".
DBCC results for 'NameValuePair_Syriac_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Syriac_90_CI_AS".
DBCC results for 'ContentTypeUsage'.
There are 33556 rows in 364 pages for object "ContentTypeUsage".
DBCC results for 'NameValuePair_Tatar_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Tatar_90_CI_AS".
DBCC results for 'NameValuePair_Uzbek_Latin_90_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Uzbek_Latin_90_CI_AS".
DBCC results for 'ContentTypes'.
There are 11868 rows in 992 pages for object "ContentTypes".
DBCC results for 'NameValuePair'.
There are 7870 rows in 92 pages for object "NameValuePair".
DBCC results for 'FeatureTracking'.
There are 1826 rows in 78 pages for object "FeatureTracking".
DBCC results for 'AllFileFragments'.
There are 0 rows in 0 pages for object "AllFileFragments".
DBCC results for 'Features'.
There are 5321 rows in 95 pages for object "Features".
DBCC results for 'Solutions'.
There are 2 rows in 1 pages for object "Solutions".
DBCC results for 'HT_Settings'.
There are 5 rows in 1 pages for object "HT_Settings".
DBCC results for 'HT_Cache'.
There are 0 rows in 0 pages for object "HT_Cache".
DBCC results for 'SolutionResourceUsageDaily'.
There are 0 rows in 0 pages for object "SolutionResourceUsageDaily".
DBCC results for 'Resources'.
There are 3579 rows in 77 pages for object "Resources".
DBCC results for 'SolutionFiles'.
There are 83 rows in 8 pages for object "SolutionFiles".
DBCC results for 'EventCache'.
There are 13952 rows in 673 pages for object "EventCache".
DBCC results for 'SolutionResourceUsageDailyOrdinal'.
There are 1 rows in 1 pages for object "SolutionResourceUsageDailyOrdinal".
DBCC results for 'SolutionResourceUsageWindowed'.
There are 0 rows in 0 pages for object "SolutionResourceUsageWindowed".
DBCC results for 'WorkflowAssociation'.
There are 28 rows in 3 pages for object "WorkflowAssociation".
DBCC results for 'CollationNames'.
There are 49 rows in 1 pages for object "CollationNames".
DBCC results for 'SolutionResourceUsageLog'.
There are 0 rows in 0 pages for object "SolutionResourceUsageLog".
DBCC results for 'EventBatches'.
There are 1 rows in 1 pages for object "EventBatches".
DBCC results for 'WebPartLists'.
There are 9330 rows in 117 pages for object "WebPartLists".
DBCC results for 'WelcomeNames'.
There are 2 rows in 1 pages for object "WelcomeNames".
DBCC results for 'Workflow'.
There are 20 rows in 1 pages for object "Workflow".
DBCC results for 'TimerLock'.
There are 1 rows in 1 pages for object "TimerLock".
DBCC results for 'Personalization'.
There are 0 rows in 0 pages for object "Personalization".
DBCC results for 'DatabaseInformation'.
There are 9 rows in 1 pages for object "DatabaseInformation".
DBCC results for 'AllWebParts'.
There are 10807 rows in 371 pages for object "AllWebParts".
DBCC results for 'ScheduledWorkItems'.
There are 0 rows in 1 pages for object "ScheduledWorkItems".
DBCC results for 'DiskWarningDate'.
There are 1 rows in 1 pages for object "DiskWarningDate".
DBCC results for 'SiteDeletion'.
There are 0 rows in 1 pages for object "SiteDeletion".
DBCC results for 'NavNodes'.
There are 1497 rows in 51 pages for object "NavNodes".
DBCC results for 'EventReceivers'.
There are 2602 rows in 188 pages for object "EventReceivers".
DBCC results for 'SiteVersions'.
There are 714 rows in 9 pages for object "SiteVersions".
DBCC results for 'CustomActions'.
There are 0 rows in 0 pages for object "CustomActions".
DBCC results for 'EventSubsMatches'.
There are 0 rows in 1 pages for object "EventSubsMatches".
DBCC results for 'SchedSubscriptions'.
There are 5 rows in 1 pages for object "SchedSubscriptions".
DBCC results for 'AuditData'.
There are 2255723 rows in 64121 pages for object "AuditData".
DBCC results for 'Deps'.
There are 0 rows in 0 pages for object "Deps".
DBCC results for 'AllUserDataJunctions'.
There are 10576 rows in 153 pages for object "AllUserDataJunctions".
DBCC results for 'WebMembers'.
There are 7974 rows in 48 pages for object "WebMembers".
DBCC results for 'GroupMembership'.
There are 1333 rows in 7 pages for object "GroupMembership".
DBCC results for 'AppPackages'.
There are 0 rows in 0 pages for object "AppPackages".
DBCC results for 'Groups'.
There are 378 rows in 16 pages for object "Groups".
DBCC results for 'ImmedSubscriptions'.
There are 16 rows in 3 pages for object "ImmedSubscriptions".
DBCC results for 'AppSourceInfo'.
There are 0 rows in 0 pages for object "AppSourceInfo".
DBCC results for 'Perms'.
There are 649 rows in 50 pages for object "Perms".
DBCC results for 'AppJobs'.
There are 0 rows in 0 pages for object "AppJobs".
DBCC results for 'AppInstallations'.
There are 0 rows in 0 pages for object "AppInstallations".
DBCC results for 'UserInfo'.
There are 7244 rows in 5694 pages for object "UserInfo".
DBCC results for 'AppLifecycleErrors'.
There are 0 rows in 0 pages for object "AppLifecycleErrors".
DBCC results for 'NameValuePair_Albanian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Albanian_CI_AS".
DBCC results for 'AppTasks'.
There are 0 rows in 0 pages for object "AppTasks".
DBCC results for 'Roles'.
There are 174 rows in 7 pages for object "Roles".
DBCC results for 'NameValuePair_Arabic_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Arabic_CI_AS".
DBCC results for 'RoleAssignment'.
There are 20415 rows in 137 pages for object "RoleAssignment".
DBCC results for 'NameValuePair_Chinese_Simplified_Pinyin_100_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_Simplified_Pinyin_100_CI_AS".
DBCC results for 'AppTaskDependencies'.
There are 0 rows in 0 pages for object "AppTaskDependencies".
DBCC results for 'AppPrincipals'.
There are 21 rows in 1 pages for object "AppPrincipals".
DBCC results for 'AppInstallationProperty'.
There are 0 rows in 0 pages for object "AppInstallationProperty".
DBCC results for 'NameValuePair_Chinese_PRC_Stroke_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_PRC_Stroke_CI_AS".
DBCC results for 'AppResources'.
There are 0 rows in 0 pages for object "AppResources".
DBCC results for 'AppPrincipalPerms'.
There are 95 rows in 1 pages for object "AppPrincipalPerms".
DBCC results for 'AppRuntimeMetadata'.
There are 0 rows in 0 pages for object "AppRuntimeMetadata".
DBCC results for 'AllListsAux'.
There are 1585 rows in 15 pages for object "AllListsAux".
DBCC results for 'NameValuePair_Chinese_Taiwan_Bopomofo_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_Taiwan_Bopomofo_CI_AS".
DBCC results for 'AppRuntimeSubstitutionDictionary'.
There are 0 rows in 0 pages for object "AppRuntimeSubstitutionDictionary".
DBCC results for 'AppRuntimeIcons'.
There are 0 rows in 0 pages for object "AppRuntimeIcons".
DBCC results for 'AllListsItemCount'.
There are 71 rows in 1 pages for object "AllListsItemCount".
DBCC results for 'NameValuePair_Chinese_Taiwan_Stroke_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_Taiwan_Stroke_CI_AS".
DBCC results for 'AppDatabaseMetadata'.
There are 0 rows in 0 pages for object "AppDatabaseMetadata".
DBCC results for 'AppSubscriptionCosts'.
There are 0 rows in 0 pages for object "AppSubscriptionCosts".
DBCC results for 'NameValuePair_Croatian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Croatian_CI_AS".
DBCC results for 'SiteHealthCheckResults'.
There are 0 rows in 0 pages for object "SiteHealthCheckResults".
DBCC results for 'AllListsPlus'.
There are 1585 rows in 31 pages for object "AllListsPlus".
DBCC results for 'PreviewSiteRequests'.
There are 0 rows in 0 pages for object "PreviewSiteRequests".
DBCC results for 'AllLookupRelationships'.
There are 429 rows in 7 pages for object "AllLookupRelationships".
DBCC results for 'NameValuePair_Cyrillic_General_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Cyrillic_General_CI_AS".
DBCC results for 'AllListUniqueFields'.
There are 17 rows in 1 pages for object "AllListUniqueFields".
DBCC results for 'NameValuePair_Czech_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Czech_CI_AS".
DBCC results for 'AllLists'.
There are 1585 rows in 89 pages for object "AllLists".
DBCC results for 'SiteUpgradeSessions'.
There are 5 rows in 6 pages for object "SiteUpgradeSessions".
DBCC results for 'NameValuePair_Danish_Norwegian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Danish_Norwegian_CI_AS".
DBCC results for 'NameValuePair_Estonian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Estonian_CI_AS".
DBCC results for 'NameValuePair_Finnish_Swedish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Finnish_Swedish_CI_AS".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'NameValuePair_French_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_French_CI_AS".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'NameValuePair_Georgian_Modern_Sort_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Georgian_Modern_Sort_CI_AS".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'SiteUserSyncQueue'.
There are 0 rows in 1 pages for object "SiteUserSyncQueue".
DBCC results for 'sys.filestream_tombstone_2073058421'.
There are 0 rows in 0 pages for object "sys.filestream_tombstone_2073058421".
DBCC results for 'NameValuePair_German_PhoneBook_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_German_PhoneBook_CI_AS".
DBCC results for 'sys.syscommittab'.
There are 0 rows in 0 pages for object "sys.syscommittab".
DBCC results for 'sys.filetable_updates_2105058535'.
There are 0 rows in 0 pages for object "sys.filetable_updates_2105058535".
DBCC results for 'BuildDependencies'.
There are 3445 rows in 137 pages for object "BuildDependencies".
DBCC results for 'NameValuePair_Greek_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Greek_CI_AS".
DBCC results for 'AllLinks'.
There are 52906 rows in 1787 pages for object "AllLinks".
CHECKDB found 0 allocation errors and 23 consistency errors in database 'Backup_of_DB'.
CHECKDB fixed 0 allocation errors and 23 consistency errors in database 'Backup_of_DB'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
===============
After this i run DBCC CHECKDB (Backup_of_DB) WITH NO_INFOMSGS, ALL_ERRORMSGS and it's clean.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
July 18, 2016 at 12:25 am
johnwalker10 (7/17/2016)
Have a look at this linkhttp://dba.stackexchange.com/questions/88982/how-to-repair-database-consistency-errors
Thanks John.
I tried almost all the minimal options (Without data loss). Tried rebuild index, REPAIR_REBUILD. What i understand from the errors, either can be restored from backup or repair_allow_data_loss.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
July 18, 2016 at 12:42 am
muthukkumaran Kaliyamoorthy (7/18/2016)
What i understand from the errors, either can be restored from backup or repair_allow_data_loss.
Yup.
If the minimum level to repair is repair_allow_data_loss then repair_rebuild is just a waste of time, the errors can only be repaired with repair_allow_data_loss
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 18, 2016 at 8:34 am
I think you should also check row count of the affected tables before and after repair_allow_data_loss.
Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising
July 18, 2016 at 9:58 am
Br. Kenneth Igiri (7/18/2016)
I think you should also check row count of the affected tables before and after repair_allow_data_loss.
Yep, Already did that. Since, There was a variation.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
July 19, 2016 at 12:30 am
This was removed by the editor as SPAM
July 19, 2016 at 1:50 am
muthukkumaran Kaliyamoorthy (7/18/2016)
Br. Kenneth Igiri (7/18/2016)
I think you should also check row count of the affected tables before and after repair_allow_data_loss.Yep, Already did that. Since, There was a variation.
Depending on the impact, you might have to live with the loss if there is no good backup or no other solution. I had a case in the past where I had to go one month back for a good backup. Scheduling DBCC CHECKDB is a very good idea. Fortunately it was a database in the pilot phase though. 😀
Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising
July 29, 2016 at 2:32 am
Br. Kenneth Igiri (7/19/2016)
muthukkumaran Kaliyamoorthy (7/18/2016)
Br. Kenneth Igiri (7/18/2016)
I think you should also check row count of the affected tables before and after repair_allow_data_loss.Yep, already did that. Since, There was a variation.
Depending on the impact, you might have to live with the loss if there is no good backup or no other solution. I had a case in the past where I had to go one month back for a good backup. Scheduling DBCC CHECKDB is a very good idea. Fortunately it was a database in the pilot phase though. 😀
Totally agreed! I have tested both options and both did not work in my case, since the application will not work for any single row mismatch. It is content DB, we used a different method from the application.
1. Restored a month old backup of DB --> count(*) of the currupted table had big variation
2. Restored DB a day old backup of DB --> run repair_allow_data_loss and the count(*) had slight variation
The DB is big and the original checkDB from the maintenance plan runs more than a day with high IOPS, I tested Ola hallengren’s checkdb with excluding non-clustered index, it runs just 6 hours. It also has an exclude table option. The script is excellent!
I always use his reindex for VLDB now the checkDB as well. The schedule is now weekly once, before a full backup.
Still, no clue about the corruption, checking with infra team 🙂
Edited: To help and understand better.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply