Post reply

DBCC CHECKDB

  • July 31, 2013 at 10:49 am

    #1637486

    L' Eomot Inversé (7/31/2013)

    and about 175 picked the equally non-existent although less implausible sounding DBCC CHECKFILEGROUP;

    http://msdn.microsoft.com/en-us/library/ms187332.aspx

    DBCC CHECKFILEGROUP (Transact-SQL)

    Checks the allocation and structural integrity of all tables and indexed views in the specified filegroup of the current database.

    Although, since CheckFilegroup wasn't an answer, I suspect you meant CheckIntegrity, which indeed does not exist.

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • July 31, 2013 at 11:13 am

    #1637493

    Interesting question, interesting discussion. Thanks, Steve!

  • July 31, 2013 at 12:34 pm

    #1637519

    kapil_kk (7/31/2013)

    Hugo Kornelis (7/31/2013)

    karuppusamy.kk (7/31/2013)

    Please clarify my following concern about this question..

    Why not DBCC CHECKIDENT?

    The short and simple answer: because Microsoft didn't build DBCC CHECKDB to include CHECKIDENT.

    The longer and more useful answer: DBCC CHECKDB is intended to test the integrity of the database. The errors it finds are the errors that can cause the database to go corrupt. If there are no corruptions in the database, DBCC CHECKDB will do nothing. If there are errors, if may attempt to repair them with as little side effects as possible.

    Contrast that the DBCC CHECKIDENT. This doesn't test for corruption; it tests for specific situations in user tables that may be a sign of inconssitencies, but definitely not of corruption. If DBCC CHECKIDENT "repairs" issues it finds, it will have a side effect on the user data (i.e. it affects identity values to be assigned in the future).

    Bottom line - DBCC CHECKIDENT is too different from the intended use of DBCC CHECKDB to be included in it.

    +1 🙂

    great explanation..

  • July 31, 2013 at 4:26 pm

    #1637604

    GilaMonster (7/31/2013)

    L' Eomot Inversé (7/31/2013)

    and about 175 picked the equally non-existent although less implausible sounding DBCC CHECKFILEGROUP;

    http://msdn.microsoft.com/en-us/library/ms187332.aspx

    DBCC CHECKFILEGROUP (Transact-SQL)

    Checks the allocation and structural integrity of all tables and indexed views in the specified filegroup of the current database.

    Although, since CheckFilegroup wasn't an answer, I suspect you meant CheckIntegrity, which indeed does not exist.

    Ouch! My fingers have betrayed me. :angry::blush::exclamation:

    Yes, I did indeed mean CHECKINTEGRITY. But it's so hard to type non-existent commands, I'm almost surprised that my fingers managed CHECKCACHE without changing it to something like DBCCFREESESSIONCACHE.

    Tom

  • August 1, 2013 at 3:01 am

    #1637689

    Thanks for the question and discussion...

  • August 1, 2013 at 6:35 am

    #1637752

    Thanks Steve. Good one.

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply