See how to avoid five incredibly painful SQL Server backup and recovery mistakes
Quest sponsored on-demand webinar
Webcast Abstract
Ensuring top notch SQL Server backup and recovery is easily attainable when you know which common mistakes to avoid. Discover what these common mistakes are in our webcast: How to Avoid Five Painful SQL Server Backup and Recovery Mistakes.
We’ll be presenting invaluable ideas culled from thousands of discussions with SQL Server administrators about their backup and recovery strategies. Join us and discover how you can avoid these common slip-ups that can make database recovery nearly impossible, and waste significant time, money, and effort, including:
- Generating excessive storage costs
- Running full and/or uncompressed backups that exceed maintenance windows
- Using flawed backup procedures that break SQL Server recovery
- Failing to optimize the actual recovery environment, prolonging restore times
- Neglecting to test key business applications after performing a restore
Speaker - David Swanson and David Gugick
David Gugick manages the LiteSpeed business for the Data Protection business unit at Dell. David brings more than 20 years of technical and management experience in application development, database design, and product and portfolio management to Dell. He previously served as Director of Software Development at Imceda Software, acquired by Quest in 2005. Prior to Imceda, David served as founder of Intrinsic Design, a consulting and application development company responsible for creating the SQL Server performance profiling product Coefficient. David also is a published author. He holds a bachelor's degree in electrical engineering from the University of Michigan. He likes coffee. Follow him on Twitter @davidgugick.
David Swanson works as a Senior Software Systems Consultant at Dell. In the past 13 years David has taken on several roles in IT including support, software development, DBA, sales engineer, product management and consultant.
To access materials please fill out the form below.
