Do's and don'ts of database corruption
Database corruption is one of the worst things you can encounter as a DBA. It can result in downtime, data loss, and unhappy users. What’s scary about corruption is that it can strike out of the blue and with no warning, and without having some way of telling if a database has become corrupt, it could be that way for months or even years before anything gets done about it.
In this session we’ll look at:
- Easy maintenance operations you should be running right now to ensure the fastest possible identification and resolution of corruption
- Best practices for handling a database that you suspect may be corrupted
- Actions that can worsen the problem
- Appropriate steps to take and options for recovery
Gail Shaw is a database specialist from Johannesburg, South Africa, specializing in performance tuning and database optimization. Gail works for Entelect, a medium-sized custom software development house based in Johannedburg. Gail is a frequent poster on the SQLServerCentral.com forums and writes for Simple-Talk. She is an MVP for SQL Server and holds the Microsoft Certified Master certification for SQL Server