"DBCC CHECKDB ... WITH DATA_PURITY" - Is it needed in SQL-2005-to-SQL-2008 upgrades?

  • Is running "DBCC CHECKDB ... WITH DATA_PURITY" necessary when upgrading a database from SQL 2005 to SQL 2008?

    Because this command can take hours for large databases, I want to avoid having to run it when upgrading SQL-2005 databases to SQL Server 2008.

    (BTW, I know if it is crucial to run it when upgrading a SQL-2000 (and earlier versions) database to sql-2005/2008).

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • On databases created in 2005, or ones from earlier versions where the data purity check has run once successfully, that option is default and all checkDB executions (excluding ones where Physical only is specified) will run the data purity checks.

    It is always a good idea to run checkdb on an upgraded database. It's not essential, you can run it at a later date, but it is a really good idea.

    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
  • I wouldn't think so, because that is only needed to enable the full checks on a database that was upgraded from 2000.

    If the database has already had that done (e.g. upgraded from 2000, now upgrading to 2008) there should be no reason to perform it again.

    If the database was created in 2005 - then again, no reason to perform the check again.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Thanks both for the input.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

Viewing 4 posts - 1 through 4 (of 4 total)

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