• You can get consistency error mostly for

    the values might be entered into the database that are not valid or out-of-range based on the data type of the column. In SQL Server 2000, DBCC CHECKDB does not perform range or integrity checks on these column values. However, in SQL Server 2005 and later, DBCC CHECKDB can detect column values that are not valid for all column data types. Therefore, running DBCC CHECKDB with the DATA_PURITY option on databases that have been upgraded from earlier versions of SQL Server might reveal preexisting column-value errors. Because SQL Server cannot automatically repair these errors, the column value must be manually updated. If CHECKDB detects such an error, CHECKDB returns a warning, the error number 2570, and information to identify the affected row and manually correct the error. (Source - Microsoft).

    My databases are on 2000 only where I believe there is no DATA_PURITY option available?

    Also, since couple of months there is no changes in any of my procs and this consistency errors start coming in just since few days.

    wouldn't it put the possibility of inserting invalid data to question?

    Apart of any disk level problem (which I am checking now) what else could be the possibility?

    -Forum Etiquette: How to post Performance Problems[/url]

    -Forum Etiquette: How to post data/code to get the best help [/url]