If you are unfortunate enough never to have read The Monster at the End of This Book (by Jon Stone, illustrated by Michael Smollin. Hopefully, suitably armed, the DBA can limit the damage caused by this much-less-friendly version of the monster at the end of the book. However, I’ll also demonstrate a few other techniques, based around the various DBCC commands, and a script that will make sure corruption issues are discovered and reported as soon as they occur, before they propagate through your data infrastructure. First and foremost, it should go without saying that not having a good backup strategy is equivalent to playing Solitary Russian Roulette. As a result of this, or some other hardware malfunction, data or indexes become corrupt on disk and can no longer be used by SQL Server, until repaired.įortunately, there are several steps you can take to protect your data, and equally important your job, in the event of data corruption. Often corruption occurs when there is a power failure and the server, rather than shutting down gracefully, simply dies in the middle of processing data. If you have been a DBA for long enough, you will have encountered the data corruption monster in at least one of its many forms. No, I am not talking about a developer I am talking about database corruption. It can strike at once or lay in wait for weeks before launching an attack. The corruption monster can be a silent and deceptive job killer.
0 kommentar(er)
