+ All Categories
Home > Documents > High Availability Options in SQL Server

High Availability Options in SQL Server

Date post: 04-Jun-2018
Category:
Upload: gopesh-vijayvergiya
View: 229 times
Download: 3 times
Share this document with a friend

of 15

Transcript
  • 8/13/2019 High Availability Options in SQL Server

    1/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    HIGH AVAILABILITY

    OPTIONS IN SQL SERVER

  • 8/13/2019 High Availability Options in SQL Server

    2/15

  • 8/13/2019 High Availability Options in SQL Server

    3/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    High Availability Definition

    + In Information Technology, high availability refers to a systemor component that is continuously operational for a desirably

    long length of time

  • 8/13/2019 High Availability Options in SQL Server

    4/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Why we really need High Availability Options ?

    + Planned Downtime

    Performing database maintenance

    Performing batch operations

    Performing an upgrade/update

    + Unplanned Downtime

    Data center failure

    Server failure

    I/O subsystem failure

    Human error

  • 8/13/2019 High Availability Options in SQL Server

    5/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    High Availability Options

    + Server Clustering/Failover Clustering

    + Log Shipping

    + Database mirroring

    + Replication

  • 8/13/2019 High Availability Options in SQL Server

    6/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Failover Clustering

    + This provides high-availability for entire instance of sql server

    + A failover cluster is setup with a minimum of two servers,where each server is called a node that are connected to a

    shared disk resource

    + Only one node is active at a time for a SQL Server instanceand serves all the requests for that instance of SQL Server

    + When the active node fails, failover takes place and one ofthe other available nodes will become the active node

  • 8/13/2019 High Availability Options in SQL Server

    7/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Failover Clustering(Contd.)

    + Pros

    Automatic failover

    Transparent client redirect

    It is the only technology that allows an entire SQL Server 2008 instance

    to be made highly available

    + Cons Does not protect against disk failure

    More expensive since it requires special hardware for the setup as well

    as redundant hardware

  • 8/13/2019 High Availability Options in SQL Server

    8/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Log Shipping

    + Log shipping is the simplest way to provide one or moreredundant copies of a single database.

  • 8/13/2019 High Availability Options in SQL Server

    9/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Log Shipping(Contd.)

    + Pros

    can be configured to multiple standby servers

    Can use compressed backup feature to limit network bandwidth

    Can be setup to use secondary server for read only activity

    No additional cost, except for the need to have another available

    server for the secondary copy

    + Cons

    no automatic failover

    Other items need to be handled outside of Log Shipping such as logins,

    SQL Agent jobs, etc... Requires additional storage for log backups and shipped copy

  • 8/13/2019 High Availability Options in SQL Server

    10/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Database Mirroring

    + Database mirroring provides a redundant copy of a singledatabase that is automatically updated with changes. The

    purpose is to ensure continuous data availability and

    minimize or avoid downtime.

  • 8/13/2019 High Availability Options in SQL Server

    11/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Database Mirroring(Contd.)

    + Operating Modes

    High Availability

    High Safety

    High Performance

    + Requirement

    Data and Log file locations should be same on both the principal and

    mirror servers

    Database name should be same on both the principal and mirror

    servers Service accounts should be same on both the instances of SQL Server

  • 8/13/2019 High Availability Options in SQL Server

    12/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Database Mirroring(Contd.)

    + Pros

    Automatic failover(only in high availability mode)

    Automatic client redirection(in all the three modes)

    Both server instances contain identical information(as per synchronous

    operation)

    Faster performance(as per asynchronous operation)

    + Cons

    Doesnt support cross-database transactions and distributed

    transactions

    Latency can slow down operation(in case of synchronous operation) In asynchronous operation, no guarantee of identical information in

    both server instances at all the times

  • 8/13/2019 High Availability Options in SQL Server

    13/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Replication

    + Replication feature in MS SQL Server moves the data from aremote server to our local server boxes via publications and

    subscriptions mechanism with the purpose to maintain

    redundant database sites.

  • 8/13/2019 High Availability Options in SQL Server

    14/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Replication(Contd.)

    + Types of replication

    Transactional Replication

    Transactional Replication with Updatable Subscriptions

    Snapshot Replication

    Merge replication

  • 8/13/2019 High Availability Options in SQL Server

    15/15

    Copyright 2011 FactSet Research Systems Inc. All rights reserved.

    Replication(Contd.)

    + Pros

    Can be configured for individual database objects instead of the entire

    database

    Provides near real time disaster recovery

    Secondary copy could be used for near real-time reporting to offload

    reporting use on production database+ Cons

    Reconfiguration may require manual intervention

    Need to rely on distributor to push changes

    Other items need to be handled outside of Replication such as logins,SQL Agent jobs, etc...


Recommended