|
I took over a database that had no maintenance jobs other than backups being done. I immediately restored the oldest backup (7 days ago) to another name and ran DBCC CHECKDB on it. It has the same number of errors and recommendation to run with repair. My question is what exactly is going to potentially be lossed. The error is an allocation error. Does that mean my data is ok, just an allocation is messed up? Thanks for any help. Running on MSSQL 2005 SP3 _____________UPDATE I have ran the repair on my restored copy of the database. Doing a row count on the table that had the error from production to the test copy gave me the same results. Is there something else I should compair? I am doing another dbcc checkdb on the database since the repair finished.
(comments are locked)
|
|
Have you run it with repair on the test copy? I think I would run it there and see what the results are like. You can get a chance to compare the test to the live data and see if anything crucial changes are made. If you can identify the changes then you can choose whether to run it on live. A great resource for DBCC CHECKDB is Paul Randall's site www.sqlskills.com so go and read up all about the options that are available with that command.
(comments are locked)
|
A simple rowcount may not show up data loss, try something like RedGate SQL Data Compare or Tablediff (http://msdn.microsoft.com/en-us/library/ms162843.aspx) to see what differences there are in the data, if any.