R L Reid (10/15/2007)
rhat (10/15/2007)
DBCC commands are wild goose chases when a siimple restore of backup is what's needed and needed ASAP.
Yes, let's just throw away the past 19 hours worth of data and overwrite. (Knock wood - I don't have issues like this because of the many layers of replication we use...but when it used to happen, there was usually discussion about how long to work on recovery before bailing out, based on business needs).
A *PROPERLY* designed system doesn't find out problems 19 hours later. A good system knows instantly, in seconds, when an error has occurred, Windows or Web, and sends an alert message to the admin and/or developer via e-mail, text message, etc......
ALSO, a properly designed database and application doesn't keep sticking bad data in the database and not let those users not know that something wrong has happening to begin with. OR, for that matter keep letting them work with a bad database for 19 hours!!!!
Secondly, it's best to go to the last known good backup just for reliability reasons. Just because you got a DBA that knows how to use DBCC doesn't' mean the database will be 100% normal again. And it could take the DBA days, weeks to figure it out and get all the errors and bad data out regardless of expertise and experience. Errors that require DBCC almost always don't just happen. There is a reason for it and it's usually BAD. And after that, there still could be problems.....i.e. wild goose chase.
Thirdly, who is to say that those 19 hours of data is GOOD data to begin with? How can one be 100% sure without rechecking it with the user who put it in there?
Four, restore is *like* using the last know good Windows OS image or the *appropriate" backup data instead of trying to get the virus out or running repair commands or wizards. In the real world, we get fast enough hardware to get this done ASAP.
Five, All that money spent on some clueless DBA that's an expert in DBCC could have been spent on faster hardware and backups to complete the job a lot faster in the end. Not to mention make the system as a whole more reliable.
But of course, DBCC, DTS and JOB SECURITY seem to go hand in hand:D