Unexpected database changes can break a system and result in unwanted down time. The first, and most important, step when this occurs is to try reversing the damage done. The sooner you know about the change, the more likely that a rollback is possible.

Speaker: K. Brian Kelley is an author, columnist, and former Microsoft SQL Server MVP, focusing primarily on SQL Server and Windows security. Besides being a database administrator, he has served as an infrastructure and security architect encompassing solutions with Citrix, virtualization, and Active Directory.

Topics: Database Administration, Database Performance, SQL Query Performance, Database Diagnostics, Database Monitoring, Database Change Management
Products: DB Change Manager