What could be the reason behind a DBCC CheckDB reporting a consistency error on a empty table in sql server 2008? This DB is restored from sql server 2000. DBCC CheckDB on sql server 2000 doesnot report any errors.
Sql-server – DBCC CheckDB Consistency error on a empty table
dbccsql server
Related Question
- Sql-server – Msg 2534 : DBCC CHECKDB allocation errors
- Sql-server – DBCC checkdb showing failure after a restore
- DBCC CHECKDB Estimation Alternative
- Sql-server – DBCC CheckDB run into early hardware failure
- DBCC CHECKDB – Consistency Error
- Sql-server – DBCC CHECKDB errors
- Sql-server – DBCC CHECKDB consistency-based I/O error
- SQL Server 2016 – Interesting DBCC CHECKDB Scenario
Best Answer
It would be a lot easier if you post what error are you getting?
Usually the corruption was already there in the 2000 version but the latest and improved version of DBCC catches the errors that werent reported by the 2000 version of DBCC. Usually running DBCC UPDATEUSAGE might fix it and if the error doesnt go away you have to check what the specific error is and try to solve it accordingly. For all things CHECKDB i suggest you dig into all paul randal checkdb related blogs.