SQL Server DATA PURITY option
SQL Server 2005 offers a new option to the DBCC CHECKDB and DBCC CHECKTABLE commands. This new option is the "DATA_PURITY" check which will look for issues where column values are not valid or out-of-range. To run the command you issue it just as you would a regular DBCC command along with the added option, such as:
DBCC CHECKDB with DATA_PURITY
For databases that are created in SQL Server 2005, these checks are on by default, so using or not using the DATA_PURITY option does not affect the outcome of the checks when issuing a DBCC CHECKDB or DBCC CHECKTABLE.
For databases that are not created in SQL Server 2005 and then later brought into SQL Server 2005 these checks are useful and will allow you to see if there are any data issues within the database. Once this is run on a databases one of two results will occur; the first it will come back clean without problems and the second there will be data issues that need to be resolved. If the purity check comes back without any problems a entry is made in the database header and whenever a DBCC CHECKDB or DBCC CHECKTABLE is issued the DATA_PURITY checks will also be performed regardless of whether you specify the DATA_PURITY check or not.
SQL Server 2005 offers a new option to the DBCC CHECKDB and DBCC CHECKTABLE commands. This new option is the "DATA_PURITY" check which will look for issues where column values are not valid or out-of-range. To run the command you issue it just as you would a regular DBCC command along with the added option, such as:
DBCC CHECKDB with DATA_PURITY
For databases that are created in SQL Server 2005, these checks are on by default, so using or not using the DATA_PURITY option does not affect the outcome of the checks when issuing a DBCC CHECKDB or DBCC CHECKTABLE.
For databases that are not created in SQL Server 2005 and then later brought into SQL Server 2005 these checks are useful and will allow you to see if there are any data issues within the database. Once this is run on a databases one of two results will occur; the first it will come back clean without problems and the second there will be data issues that need to be resolved. If the purity check comes back without any problems a entry is made in the database header and whenever a DBCC CHECKDB or DBCC CHECKTABLE is issued the DATA_PURITY checks will also be performed regardless of whether you specify the DATA_PURITY check or not.