Chapter 9. Implementing High Availability


Terms you'll need to understand:

Database mirroring

Log shipping

Witness

Secondary database

Replication

Publisher

Distributor

Subscriber

Latency

Failover

Clustering

Data mart

Data warehouse

Techniques you'll need to master:

Utilizing database mirroring with and without a witness

Setting up, initiating, and implementing log shipping

Defining replication and designing the replication architecture

Defining clustering, data mart, and data warehouse

Understanding techniques for controlling latency

High availability is important in most database systems. Having data available 24 hours a day, 7 days a week, every day of the year is important in many environments. Every database administrator aims at achieving the elusive "five nines," which means the system is up, running, and available to users 99.999% of the time.

In addition to being available, a system must perform well. High availability also means that the server, its hardware, and the database configuration perform well within the system. Response times must be sufficient. Transaction speeds must be maintained.

A truly available environment must achieve five-nines reliability while receiving a passing mark in performance.




MCTS 70-431(c) Implementing and Maintaining Microsoft SQL Server 2005
MCTS 70-431 Exam Cram: Implementing and Maintaining Microsoft SQL Server 2005 Exam
ISBN: 0789735881
EAN: 2147483647
Year: 2006
Pages: 200
Authors: Thomas Moore

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net