July 23, 2012 at 9:06 am
I ran Ola's original script, with the data purity arg. Fortunately this is a UAT server, so it didn't affect Prod, but because of that the usage is much lower and this is one reason it troubled me that it was taking so long.
Ola's script is written to give only error messages, so I would not see any informational messages. When
I ran it for 8 hours on Thursday I was just running DBCC CheckDB(Dmart_MSRIPOS), which should have given me regular informational messages as it worked its way through. It doesn't do it quite table by table, but I expected every hours or so, to have it report back to the query window what it had done so far.
I did not check the boot page before the successful completion of CheckDb. Here are the current result though.
DBINFO STRUCTURE:
DBINFO @0x6470EF7C
dbi_dbid = 7 dbi_status = 65544 dbi_nextid = 2021686350
dbi_dbname = DMART_MSRIPOS dbi_maxDbTimestamp = 122200 dbi_version = 611
dbi_createVersion = 539 dbi_ESVersion = 0
dbi_nextseqnum = 1900-01-01 00:00:00.000 dbi_crdate = 2008-10-27 11:11:22.720
dbi_filegeneration = 0
dbi_checkptLSN
m_fSeqNo = 225290 m_blockOffset = 1696 m_slotId = 25
dbi_RebuildLogs = 0 dbi_dbccFlags = 2
dbi_dbccLastKnownGood = 2012-07-21 00:23:36.270
dbi_dbbackupLSN
m_fSeqNo = 214277 m_blockOffset = 392198 m_slotId = 1
dbi_oldestBackupXactLSN
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_LastLogBackupTime = 2008-10-27 14:33:49.347
dbi_differentialBaseLSN
m_fSeqNo = 216905 m_blockOffset = 871 m_slotId = 64
dbi_createIndexLSN
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_versionChangeLSN
m_fSeqNo = 189359 m_blockOffset = 21 m_slotId = 1
dbi_familyGUID = 7398ef06-695c-4bfd-bca4-93b1dfe8eb97
dbi_recoveryForkNameStack
entry 0
m_fSeqNo = 214277 m_blockOffset = 392198 m_slotId = 1
m_guid = 922f9481-ffb8-4b7b-9dec-9f5ed6d93785
entry 1
m_fSeqNo = 214277 m_blockOffset = 392198 m_slotId = 1
m_guid = ebeb9bd7-cc0a-4813-ae81-e103af225b25
dbi_differentialBaseGuid = 6d81afb0-c465-49bb-a079-cc618ad9e8d4 dbi_firstSysIndexes = 0001:0000000f
dbi_collation = 872468488 dbi_category = 0 dbi_maxLogSpaceUsed = 193712077312
dbi_localState = 0 dbi_roleSequence = 0
dbi_failoverLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_dbmRedoLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_dbmOldestXactLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_dbMirrorId = 00000000-0000-0000-0000-000000000000
dbi_pageUndoLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_disabledSequence = 0
dbi_dvSplitPoint
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_CloneCpuCount = 0 dbi_CloneMemorySize = 0
Thanks,
Chris
Learning something new on every visit to SSC. Hoping to pass it on to someone else.
July 23, 2012 at 9:56 am
What does the boot page say in prod?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 23, 2012 at 12:03 pm
Prod:
DBINFO @0x6902EF8C
dbi_dbid = 211 dbi_status = 65544 dbi_nextid = 1109683101
dbi_dbname = DMART_MSRIPOS dbi_maxDbTimestamp = 114200 dbi_version = 611
dbi_createVersion = 539 dbi_ESVersion = 0
dbi_nextseqnum = 1900-01-01 00:00:00.000 dbi_crdate = 2008-11-25 15:27:17.847
dbi_filegeneration = 0
dbi_checkptLSN
m_fSeqNo = 384680 m_blockOffset = 23866 m_slotId = 5
dbi_RebuildLogs = 0 dbi_dbccFlags = 0
dbi_dbccLastKnownGood = 1900-01-01 00:00:00.000
dbi_dbbackupLSN
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_oldestBackupXactLSN
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_LastLogBackupTime = 1900-01-01 00:00:00.000
dbi_differentialBaseLSN
m_fSeqNo = 383243 m_blockOffset = 21198 m_slotId = 145
dbi_createIndexLSN
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_versionChangeLSN
m_fSeqNo = 189359 m_blockOffset = 21 m_slotId = 1
dbi_familyGUID = 7398ef06-695c-4bfd-bca4-93b1dfe8eb97
dbi_recoveryForkNameStack
entry 0
m_fSeqNo = 215818 m_blockOffset = 103621 m_slotId = 1
m_guid = b71351a0-247f-4175-a603-a752d2683915
entry 1
m_fSeqNo = 215818 m_blockOffset = 103621 m_slotId = 1
m_guid = ebeb9bd7-cc0a-4813-ae81-e103af225b25
dbi_differentialBaseGuid = b769bdfc-3791-4b39-9325-096a9a216acd dbi_firstSysIndexes = 0001:0000000f
dbi_collation = 872468488 dbi_category = 0 dbi_maxLogSpaceUsed = 193712077312
dbi_localState = 0 dbi_roleSequence = 0
dbi_failoverLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_dbmRedoLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_dbmOldestXactLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_dbMirrorId = 00000000-0000-0000-0000-000000000000
dbi_pageUndoLsn
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_disabledSequence = 0
dbi_dvSplitPoint
m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
dbi_CloneCpuCount = 0 dbi_CloneMemorySize = 0
Learning something new on every visit to SSC. Hoping to pass it on to someone else.
July 23, 2012 at 1:01 pm
Stamey (7/23/2012)
m_fSeqNo = 384680 m_blockOffset = 23866 m_slotId = 5dbi_RebuildLogs = 0 dbi_dbccFlags = 0
dbi_dbccLastKnownGood = 1900-01-01 00:00:00.000
dbi_dbbackupLSN
DB has never had a successful CheckDB.
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 23, 2012 at 1:06 pm
GilaMonster (7/23/2012)
Stamey (7/23/2012)
m_fSeqNo = 384680 m_blockOffset = 23866 m_slotId = 5dbi_RebuildLogs = 0 dbi_dbccFlags = 0
dbi_dbccLastKnownGood = 1900-01-01 00:00:00.000
dbi_dbbackupLSN
DB has never had a successful CheckDB.
I looked at all databases I had access to. I even pulled up some backups of databases upgraded from 2000 before they had checkdb run and could not find one with dbi_dbccFlags = 1 so I am not sure how that flag is ever set to that value. Last known good date is definitely the one to use.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply