November 29, 2016 at 3:35 pm
CHECKDB has found corruption on one of our production databases (running SQL Server 2012), but it returns more errors when ran against a backup and restore of the database onto two independent SQL 2016 servers. I've read that CHECKDB is faster on SQL 2016 because it doesn't run as many checks [source][/url]
Could someone please explain why I'm seeing more errors when ran against SQL 2016?
The command I'm running is
DBCC CHECKDB (SPSProd_Content_M) WITH NO_INFOMSGS, ALL_ERRORMSGS
On the production environment, and a backup and restore to another SQL2012 server the last line of CHEKDB reads:
CHECKDB found 75 allocation errors and 1 consistency errors in database 'SPSM'.
On a backup and restore to two SQL 2016 servers, the last line reads:
CHECKDB found 75 allocation errors and 491 consistency errors in database 'SPSM'.
The added rows are in the below format:
Msg 8939, Level 16, State 98, Line 51
Table error: Object ID 862626116, index ID 1, partition ID 72057594081968128, alloc unit ID 72057594097106944 (type In-row data), page (1:105144). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8909, Level 16, State 1, Line 51
Table error: Object ID 926626344, index ID 1, partition ID 72057594082230272, alloc unit ID 72057594055688192 (type LOB data), page ID (1:15007) contains an incorrect page ID in its page header. The PageId in the page header = (1:5713311).
Msg 8906, Level 16, State 1, Line 51
Page (1:15000) in database ID 32 is allocated in the SGAM (1:3) and PFS (1:8088), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Msg 8906, Level 16, State 1, Line 51
November 29, 2016 at 9:25 pm
This was removed by the editor as SPAM
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply