Building Highly Available Systems with SQL Server™ 2005 Vineet Gupta Evangelist – Data and Integration Microsoft Corp.

Slides:



Advertisements
Similar presentations
Avanade: Tid for oppetid
Advertisements

Mecanismos de alta disponibilidad con Microsoft SQL Server 2008 Por: ISC Lenin López Fernández de Lara.
High Availability Group 08: Võ Đức Vĩnh Nguyễn Quang Vũ
High Availability David Frommer Principal Architect Business Intelligence Microsoft Partner of the Year 2005 & 2007.
Oracle Data Guard Ensuring Disaster Recovery for Enterprise Data
FlareCo Ltd ALTER DATABASE AdventureWorks SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS Slide 1.
SQL Server 2005 features for VLDBs. SQL Server 2005 features for VLDBs aka (it’s fixed in the next release)
DataBase Administration Scheduling jobs Backing up and restoring Performing basic defragmentation and index rebuilding Using alerts Archiving.
Vinod Kumar Technology Evangelist | Microsoft
1 © Copyright 2010 EMC Corporation. All rights reserved. EMC RecoverPoint/Cluster Enabler for Microsoft Failover Cluster.
SQL Server Data Protection and High Availability Anil Desai.
Keith Burns Microsoft UK Mission Critical Database.
SQL Server 2005 Administration, Scalability and Reliability Dr Greg Low Readify
1© Copyright 2011 EMC Corporation. All rights reserved. EMC RECOVERPOINT/ CLUSTER ENABLER FOR MICROSOFT FAILOVER CLUSTER.
Meeting the Availability Challenge Don Vilen Program Manager SQL Server Microsoft Corporation.
SQL Server High Availability
Backup and Recovery Part 1.
National Manager Database Services
Database Configuration and Maintenance Database Configuration and Maintenance Exam / 30.
Chapter 2 Administrating DB Engine. Database Engine  The Database Engine is the core service for storing, processing, and securing data.  It provides.
Building Highly Available Systems with SQL Server™ 2005 Robert Rea Brandon Consulting.
1 Data Guard Basics Julian Dyke Independent Consultant Web Version - February 2008 juliandyke.com © 2008 Julian Dyke.
Chapter 10 : Designing a SQL Server 2005 Solution for High Availability MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design.
Implementing Database Snapshot & Database Mirroring in SQL Server 2005 Presented by Tarek Ghazali IT Technical Specialist Microsoft SQL Server MVP Microsoft.
High-Availability Methods Lesson 25. Skills Matrix.
Maintaining a Microsoft SQL Server 2008 Database SQLServer-Training.com.
Stephan Hurni Consultant Trivadis AG, SQL Server notes from the field.
SQL-Server 2012 Always On.
Chapter 2: Designing Physical Storage MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design Study Guide (70-443)
Sofia, Bulgaria | 9-10 October SQL Server 2005 High Availability for developers Vladimir Tchalkov Crossroad Ltd. Vladimir Tchalkov Crossroad Ltd.
Maintaining a Mirrored Database Tips and Tricks by Paul G. Hiles.
16 Copyright © 2007, Oracle. All rights reserved. Performing Database Recovery.
4 Copyright © 2006, Oracle. All rights reserved. Recovering from Noncritical Losses.
11g(R1/R2) Data guard Enhancements Suresh Gandhi
DATABASE MIRRORING  Mirroring is mainly implemented for increasing the database availability.  Is configured on a Database level.  Mainly involves two.
Rajib Kundu Agenda Definitions Failover Cluster Database Snapshots Log shipping Database Mirroring.
1 Data Guard. 2 Data Guard Reasons for Deployment  Site Failures  Power failure  Air conditioning failure  Flooding  Fire  Storm damage  Hurricane.
Module 16: Performing Ongoing Database Maintenance
Module 13 Implementing Business Continuity. Module Overview Protecting and Recovering Content Working with Backup and Restore for Disaster Recovery Implementing.
Pedro Azevedo Lopes Premier Field Engineer Microsoft Corporation.
Building Highly Available Systems with SQL Server™ 2005 Keith Burns Data Architect Microsoft Ltd.
14 Copyright © 2005, Oracle. All rights reserved. Backup and Recovery Concepts.
High Availability in DB2 Nishant Sinha
Oracle DBAs Deploying Highly Available SQL Server Systems
Connect with life Vinod Kumar Technology Evangelist - Microsoft
Enhancing Scalability and Availability of the Microsoft Application Platform Damir Bersinic Ruth Morton IT Pro Advisor Microsoft Canada
18 Copyright © 2004, Oracle. All rights reserved. Backup and Recovery Concepts.
6 Copyright © 2007, Oracle. All rights reserved. Performing User-Managed Backup and Recovery.
Course Topics Administering SQL Server 2012 Jump Start 01 | Install and Configure SQL Server04 | Manage Data 02 | Maintain Instances and Databases05 |
Backup and Recovery - II - Checkpoint - Transaction log – active portion - Database Recovery.
Danny Tambs – Senior Consultant Microsoft.
Your Data Any Place, Any Time Always On Technologies.
Virtual Machine Movement and Hyper-V Replica
1 Chapter Overview Using Standby Servers Using Failover Clustering.
Praveen Srivatsa Director| AstrhaSoft Consulting blogs.asthrasoft.com/praveens |
Log Shipping, Mirroring, Replication and Clustering Which should I use? That depends on a few questions we must ask the user. We will go over these questions.
Digging Out From Corruption Eddie Wuerch, MCM - Principal, Database Performance - Salesforce Marketing Cloud Data protection and loss recovery with SQL.
6 Copyright © Oracle Corporation, All rights reserved. Backup and Recovery Overview.
William Durkin A Gourmet Menu of SQL Server High Availability Options.
Sponsors.
Database Administration
Navigating the options for Data Redundancy
AlwaysOn Mirroring, Clustering
Maximum Availability Architecture Enterprise Technology Centre.
A Technical Overview of Microsoft® SQL Server™ 2005 High Availability Beta 2 Matthew Stephen IT Pro Evangelist (SQL Server)
Required 9s and data protection: introduction to sql server 2012 alwayson, new high availability solution Santosh Balasubramanian Senior Program Manager.
SQL Server High Availability Amit Vaid.
Your Data Any Place, Any Time
Performing Database Recovery
Designing a Highly Available SQL Server Infrastructure
Presentation transcript:

Building Highly Available Systems with SQL Server™ 2005 Vineet Gupta Evangelist – Data and Integration Microsoft Corp.

Availability What does it mean to you?  Why not?  Site is unavailable  System is unavailable  Database is unavailable  Database is partially unavailable  Table is unavailable  Data is unavailable Can your customers get done, what they need to get done, when they need to do it? 24x7x365

Barriers To Availability  Database Maintenance and Operations  Data Access Concurrency Limitations  Database Server Failure or Disaster

Barriers To Availability  Database Maintenance and Operations  Fast Recovery  Partial Availability  Online Restore  Media Reliability  Dedicated Administration Connection  Dynamic Configuration  Data Access Concurrency Limitations  Database Server Failure or Disaster

What happens when…  Disks Fail  In SQL Server™ 2000  Database is marked suspect  Users are unable to access the database  In SQL Server™ 2005  Filegroup is marked offline  Users are able to access undamaged data

Partial Database Availability Improving Availability for Isolated Disaster  Undamaged data remains available while damaged data is inaccessible  File Status shown in sys.database_files catalog view  Page Errors written to suspect_pages table in msdb  Agent alerts:  Notification of the damaged file  Can take the database offline, if desired  Can automate the restore, for read-only data

What happens when…  Recovery begins  In SQL Server™ 2000  Database is in a restoring state  Users are unable to access the database  File needs to be recreated and zero initialized  File Restore can proceed – offline  In SQL Server™ 2005  Filegroup is in a restoring state  Users are able to access undamaged data  File can be recreated with instant file Initialization  Piecemeal Restore can proceed – online

Online Piecemeal Restore Improving Availability during Recovery  Almost any component (page, file, filegroup) can be restored – ONLINE  If a page is damaged – restore only that page from a file, filegroup or database backup  If a file is damaged – restore only that file from a file, filegroup or database backup  If a filegroup is damaged – restore only that filegroup from a filegroup or database backup  Readonly filegroups can be restored without rolling forward log changes  Users can access the database during the restore

Partial Database Availability Online Piecemeal Restore

Summary: Maintenance and Ops TechnologyImprovesWhen Partial Database Availability  Data Availability Undamaged data/partitions remains available  Recovery Time Recover only that which is damaged Upgrade Immediate Instant File Initialization  Database Creation Time Files are not zero-initialized  File, Filegroup, and Database Restore Missing files are created quickly  Autogrow and Manual Growth time Additional space is quickly added  Recovery Time – Less time to create files Upgrade Immediate Online Piecemeal Restore  Data Availability Undamaged data/partitions remains available during recovery  Recovery Time Recover only that which is damaged – online Upgrade Immediate

Barriers To Availability  Database Maintenance and Operations  Data Access Concurrency Limitations  Snapshot Isolation  Online Index Operations  Replication  Data Partitioning  Database Server Failure or Disaster

What happens when…  Indexes need to be rebuilt  In SQL Server™ 2000  Index rebuilds require an exclusive table-level lock, resulting in offline rebuilds  Users are unable to access the table  In SQL Server™ 2005  Rebuilds of an index can be performed online if a few simple criteria are met  Users are able to access the table

Online Index Operations Improving Concurrency during Index Maintenance  SQL Server™ 2000  Offline Index Rebuilds ; table data is unavailable during operation  Rebuild options: DBCC DBREINDEX and CREATE with DROP_EXISTING  SQL Server™ 2005  Includes all of the above offline operations, plus…  New ALTER INDEX…REBUILD:  ONLINE – allows concurrent user access (queries as well as modifications) to the index during rebuild  OFFLINE – works using locks (same as SQL Server™ 2000)  If online is not possible by default, consider design alternatives to fully leverage online index rebuilds

Online Index Rebuilds

What happens when…  Readers and Writers desire the same data  In SQL Server™ 2000  Locking is used to guarantee the intended level of isolation  Users must wait to access locked data  Concurrency and performance compromised  Correctness is compromised when lower isolation levels are used to avoid locking  In SQL Server™ 2005  Locking OR Versioning can be used to guarantee a variety of isolation levels  With versioning, Readers won’t block writers and writers won’t block readers  Performance improved if contention was primary bottleneck  Correctness is not compromised due to use of lower isolation levels

Snapshot Isolation Improving Concurrency in Mixed Workloads  SQL Server™ 2000  Isolation implemented solely through locking  Mixed workloads may experience:  Concurrency problems due to blocking  The Inconsistent Analysis problem  SQL Server™ 2005  Isolation implemented using locking and versioning  Mixed workloads can improve read consistency and performance using:  Read committed with Statement-level snapshot to improve statement-level consistency  Snapshot Isolation to improve transaction-level consistency

Snapshot Isolation

Barriers To Availability  Database Maintenance and Operations  Data Access Concurrency Limitations  User or Application Error  Database Server Failure or Disaster  Failover Clustering  Database Mirroring  Peer-to-Peer Replication  Log Shipping

Database Mirroring Database-level Redundancy  Upcoming High Availability Technology  Released for testing and prototyping in SQL Server™ 2005 RTM  Certified for Production Use in the first half of 2006  Supports three configurations:  High Availability  High Protection  High Performance

Commit Write to Local Log Transmit to Mirror Write to Remote Log Acknowledge Committed in Log Constantly Redoing on Mirror Acknowledge Database Mirroring Log DB Log

Database Mirroring Configuration Summary  No Automatic Detection  Manual Failover  Uses synchronous form of mirroring  Does not require Witness  Principal performance is affected by network speed and distance High Availability High Protection High Performance  Automatic Detection  Automatic Failover  Uses synchronous form of mirroring  Requires Witness  Principal performance is affected by network speed and distance  No Automatic Detection  Manual Failover  Uses asynchronous form of mirroring  Does not require Witness  Principal performance is NOT affected by network speed and distance

Database Mirroring

Which Technology When? Downtime – Time to Detect, Failover/Recover and Resume Workload s e c o n d s to m i n u t e s to h o u r s to d a y s Failover Clustering Database Mirroring Database Mirroring High Availability Configuration Workloss Exposure – Amount of Potential Data Loss none to seconds tominutes to days Workloss Exposure – Amount of Potential Data Loss none to seconds to minutes to days Failover Clustering Geographically Dispersed Database Mirroring Database Mirroring High Performance Configuration Replication Peer-to-Peer Transactional Log Shipping Backup/Restore Backup/Restore Online Page-level to File-level to Filegroup-level to Offline Database Detach/Attach Database Snapshot

Summary: Standby Technologies TechnologyStandbyProtectionWhen Failover Clustering HotServer Minimal Work to Leverage Database Mirroring High Availability Configuration HotDatabase Minimal Work to Leverage Log Shipping WarmDatabase Minimal Work to Leverage Database Mirroring High Protection Configuration WarmDatabase Minimal Work to Leverage Database Mirroring High Performance Configuration WarmDatabase Minimal Work to Leverage ReplicationWarm Database (Publication of objects) Design and Architect Partial Database Availability OnlineFilegroup/File Upgrade Immediate Backup and Restore Cold Database Filegroup/File Upgrade Immediate

Barriers To Availability How SQL Server 2005 Addresses Them  Database Maintenance and Operations  Fast Recovery  Partial Availability  Online Restore  Media Reliability  Dedicated Administration Connection  Dynamic Configuration  Data Access Concurrency Limitations  Snapshot Isolation  Online Index Operations  Replication  Data Partitioning  Database Server Failure or Disaster  Failover Clustering  Database Mirroring  Peer-to-Peer Replication  Log Shipping

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.