Potential database disasters can arise from natural causes like floods and hurricanes, to user errors, to media or hardware failure. The process of disaster recovery involves mitigating the likelihood of a disaster and the process of returning the system to a normal state. It is intricately linked with the important areas of availability and business continuity, which ensure day-to-day activities can continue regardless of the problem.
This book shows readers how to implement an effective disaster recovery strategy for SQL Server 2005 and 2008 databases. It details powerful tools and features for data backup and disaster recovery, such as Database Snapshots and Mirroring, which are present in SQL Server 2005 and enhanced in SQL Server 2008. Written by an acknowledged expert in the field who has high community recognition, it covers all new 2005 and 2008 features, with broad appeal to users of SQL Server 2000 on up as well as third-party database users.
Auflage
Sprache
Verlagsort
Zielgruppe
Für Beruf und Forschung
Popular/general
Produkt-Hinweis
Illustrationen
Maße
Höhe: 260 mm
Breite: 183 mm
Dicke: 24 mm
Gewicht
ISBN-13
978-1-59059-967-9 (9781590599679)
DOI
10.1007/978-1-4302-0601-9
Schweitzer Klassifikation
James Luetkehoelter is an MSCE, MSCD, MCDBA, MCT, and Oracle Certified Professional who has been working in the database field for more than a decade. He is currently the principle consultant and owner of Spyglass LLC, a data-centric consulting company. James is a frequent presenter at SQL Server conferences, both in the U.S. and in Europe. His teaching and presenting style is best described as "eclectic," though some may say "just plain goofy." In his spare time, he catalogues the various pronunciations of "Luetkehoelter." He is currently at 2,017 distinct variations.
What Is Disaster Recovery?.- Making Database Backups.- Restoring a Database.- Backing Up and Restoring Files and Filegroups.- Creating a Backup/Recovery Plan.- Maintaining a Warm Standby Server via Log Shipping.- Clustering.- Database Mirroring.- Database Snapshots.- Hardware Considerations.- Disaster Recovery Planning.- Realistic Disaster Recovery Planning.