Packt.Microsoft.SQL.Server.2008.High.Availability.2011

preview
试读
308页
MSSQL
Server
2008
需积分: 0 6 下载量 169 浏览量 更新于2011-06-14 收藏 12.84MB PDF 举报
《Microsoft SQL Server 2008 高可用性》一书深入探讨了SQL Server 2008在确保数据高可用性和可靠性方面的关键概念和技术。本书由Hemant Giri S. Goswami撰写，他是该领域的专业专家，旨在帮助读者掌握数据库镜像、日志传送、集群和复制等高级技术，从而实现SQL Server应用程序的最小停机时间，加速恢复过程，并达到最高水平的可用性和可靠性。 ### 数据库镜像(Database Mirroring) 数据库镜像是SQL Server提供的一个高可用性解决方案，它通过在两台服务器之间实时复制事务日志，使主数据库（生产数据库）和镜像数据库保持同步。当主数据库出现故障时，镜像数据库可以立即接管，提供连续的服务。这种技术特别适合那些对数据丢失容忍度低且需要快速恢复的应用场景。 ### 日志传送(Log Shipping) 日志传送是一种将事务日志从一个数据库（主数据库）传送到另一个或多个数据库的技术，这些接收日志的数据库被称为备用数据库。通过定期备份和恢复事务日志，日志传送可以构建一个或多个备用数据库，用于灾难恢复或报表处理。与数据库镜像相比，日志传送提供了更大的灵活性，但恢复时间可能较长。 ### 集群(Clustering) 集群是通过将多台服务器连接在一起形成一个集群，共同为用户提供服务，以此提高系统的可用性和性能。在SQL Server中，集群通常用于实现高可用性和负载均衡。当集群中的某一台服务器发生故障时，集群管理器会自动将服务切换到另一台健康的服务器上，从而保证服务的连续性。 ### 复制(Replication) 复制是一种将数据从一个数据库（发布者）复制到一个或多个其他数据库（订阅者）的技术，主要用于数据分发和异构环境下的数据集成。SQL Server支持多种复制类型，包括快照复制、事务复制和合并复制，每种类型都有其特定的应用场景。复制不仅可以用于数据分发，还可以用于灾难恢复和报表处理等。 ### 结论 《Microsoft SQL Server 2008 高可用性》一书不仅详细介绍了数据库镜像、日志传送、集群和复制等高可用性技术的概念和操作方法，还包含了大量实战案例和最佳实践，对于希望提升SQL Server系统可用性和可靠性的DBA、开发者和架构师来说，是一本不可多得的实用指南。通过学习和应用书中的知识，可以有效地降低业务中断的风险，保障数据的安全和完整性，提高企业的核心竞争力。
Microsoft SQL Server 2008
High Availability
Minimize downtime, speed up recovery, and achieve
the highest level of availability and reliability for
SQL server applications by mastering the concepts
of database mirroring, log shipping, clustering,
and replication
Hemantgiri S. Goswami
professional expertise distilled
BIRMINGHAM - MUMBAI
Microsoft SQL Server 2008 High Availability
Copyright © 2011 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, without the prior written
permission of the publisher, except in the case of brief quotations embedded in
critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy
of the information presented. However, the information contained in this book is
sold without warranty, either express or implied. Neither the author, nor Packt
Publishing, and its dealers and distributors will be held liable for any damages
caused or alleged to be caused directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all of the
companies and products mentioned in this book by the appropriate use of capitals.
However, Packt Publishing cannot guarantee the accuracy of this information.
First published: January 2011
Production Reference: 2170111
Published by Packt Publishing Ltd.
32 Lincoln Road
Olton
Birmingham, B27 6PA, UK.
ISBN 978-1-849681-22-3
www.packtpub.com
Cover Image by Mark Holland (mJH767@bham.ac.uk)
Credits
Author
Hemantgiri S. Goswami
Reviewers
Adam Haines
Deepak Vohra
Development Editor
Maitreya Bhakal
Technical Editor
Gaurav Datar
Copy Editors
Leonard D'Silva
Janki Mathuria
Indexer
Monica Ajmera Mehta
Editorial Team Leader
Gagandeep Singh
Project Team Leader
Ashwin Shetty
Project Coordinator
Joel Goveya
Proofreader
Mario Cecere
Graphics
Geetanjali Sawant
Production Coordinator
Shantanu Zagade
Cover Work
Shantanu Zagade
Foreword
Every new version of SQL Server brings with it new tools and features for database
administrators (DBAs), developers, and architects, for them to be able to provide
an effective solution for the end users in a simpler and more efcient manner. The
terms effective and efciency can be measured in a technical perspective as High
Availability (HA) and Disaster Recovery (DR).
Let's assume that a world-wide retailer's CTO has been tasked to provide high
availability for their mission-critical back-end systems that are built upon SQL
Server technologies. It is a major task for DBAs to implement an HA solution on a
SQL Server data platform, and for developers to ensure that underlying application
architecture is HA-aware to take advantage of mission-critical features from SQL
Server technologies.
SQL Server High Availability features include failover clustering, database
mirroring, log shipping, replication, and backup and restore strategies. The solution
must t within the company's budget, keeping up the scalability, and should reduce
degradation in performance. When it comes to the disaster recovery solution, it may
not be possible for the primary and secondary site's hardware to be the same, such
as fewer hardware resources, limited storage capacity, or data center limitations. It
may be acceptable to the business in terms of costing, but when a disaster strikes, the
damage will be irrecoverable. All such out-of-the-box limitations must be avoided, or
reduced, to keep up the mission-critical applications always online.
The most critical aspect of any high-availability solution is designing a failback
(quick recovery of data) strategy, that is, the application must be designed to direct
the connections to the available instance when the SQL Server instance fails over to
the secondary server in a seamless manner. Though SQL Server is an out-of-the-box
disaster recovery tool, many of them are limited to traditional methods of backup
and restore functionality that are time consuming during a recovery event. So,
the new trend in the industry is to replace the existing older backup and restore
policies, taking advantage of hardware capabilities as a DR solution. This requires
server-class hardware and standardization on same hardware, but still lacks the
quicker data recovery strategy.

剩余307页未读，继续阅读

资源推荐
资源评论
DoomLord
  • 粉丝: 114
  • 资源: 1317
上传资源 快速赚钱
voice
center-task 前往需求广场，查看用户热搜

最新资源