Sql server 2012 - always on deep dive - bob duffy

4,150 views
3,874 views

Published on

http://sqlbits.com/Sessions/Event9/SQL_Server_Denali-Always_On_Deep_Dive

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,150
On SlideShare
0
From Embeds
0
Number of Embeds
432
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Slide ObjectiveHighlight major changes in the platform:There are new highavailability solutions.Performance was a major focus.Reducing cost and increasing flexibility were also major goals.Speaker ScriptWe have looked at just some of the changes coming in SQL Server “Denali.” As you can see, Microsoft has focused on making SQL Server the best database for mission-critical workloads with high availability improvements. Taking the current global economic situation, Microsoft has added features that let you do more with your existing investments in hardware, software, and training. Another focus has been to introduce holistic features that prevent the need for additional software or solutions. The end result is that SQL Server “Denali” can help you run your business better, giving you increased visibility into all the data that you collect so that you can turn into actionable knowledge.
  • With AlwaysOn we are introducing a new capability called Availability group. Availability Group provides HA and DR for application databases. Availability Group provides you with a rich set of options that provide flexibility in configuration- Talk through optionsApart from these options AG also gives you improved efficiency and integrated experience.- Talk through options
  • Sql server 2012 - always on deep dive - bob duffy

    1. 1. 23rd May 2012SQL Server 2012 – Always On Deep Dive Bob Duffy Database Architect Prodata SQL Centre of Excellence
    2. 2. Speaker Profile – Bob Duffy• Database Architect at Prodata SQL Centre Excellence, Dublin• One of about 25 MCA for SQL Server globally (aka SQL Ranger)• SQL Server MVP, 2009+• MCM on SQL 2005 and 2008• 20 years in database sector, 250+ projects• Senior SQL Consultant with Microsoft 2005-2008• Blog http://blogs.prodata.ie/bob
    3. 3. Agenda• Typical HADR Requirements• Always On Installation• Migrating to Availability Groups• Planned Failover• Automated Failover• Active Secondary Replicas• Integration with Failover Clustering
    4. 4. Case Study – Dell DVD Store Enterprises Need to accept 24 x 7 transactions For High Availability Zero down time and data loss (automatic) SLA to cover storage failure “I see web site unavailable and you are fired” “Reporting” Near real time. No more than 1 minute behind With minimal impact on live transactions Disaster Recovery Have second data centre. No more than 30 mins down time and 5 minutes data loss Upgrade Any upgrade needs to be with no down time or data loss
    5. 5. Typical HA/DR/Reporting ArchitectureApplication Server(s) DR Site
    6. 6. Denali Always On Synchronous Secondary Replica (Automatic)Application Server(s) Asynchronous Secondary Replica Read Only DR Site Secondary Replica (Manual Async)
    7. 7. Installation Always On relies on WSFC Always On is NOT a clustered install of SQL Does not need Shared Disk Windows 2008 Server+ EE needed Need to Enable HadrService Via configuration manager Or via PowerShell Some Patches and QFE Needed KB 976097 KB 2494036
    8. 8. InstallationCluster + HadrService
    9. 9. Migrating to Always On / Denali Any normal migration is possible: Backup / Restore Attach / Detach Mirroring Log Shipping Replication Might need some post migration tasks Compatibility Use of new features such as Containment
    10. 10. Migrating to Denali
    11. 11. Creating your FirstAvailability Group
    12. 12. Failover to Secondary
    13. 13. Quorum Changes Required for automatic failover Built in feature of WSFC Replaces the concept of “witness” to avoid split brain Two recommended Steps 1. Select nodes to vote 2. Select the Quorum Type If Odd number use “Node Majority” If even number use “Node Majority plus File Share Witness” Requires QFE KB KB 2494036 to enable Voting May need to adjust quorum after failover outside automatic target
    14. 14. Flexible Failover PolicyFlexible Failover Policy provides administrators control over theconditions when an automatic failover should be initiated. Diagnostics Configurable options eliminate false failover Improved logging for better diagnostics
    15. 15. New Failure Condition LevelsLevel Condition Description0 No Automatic Failure Maintenance Mode1 Failover or restart on SQL Server down Service Down2 Failover or restart on SQL Server No data from unresponsive sp_server_diagnostics3* Failure of restart of critical Services sp_server_diagnostics Return „system error‟4 Failover or restart on moderate server sp_server_diagnostics errors Return „resource error‟5 Failover or restart on any qualified failure sp_server_diagnostics conditions Return „query processing error‟
    16. 16. Automated Failover
    17. 17. Secondary Replica Features Failover Backup DBCC Reporting Queries AlwaysOn AutoStat Automatic Page Repair
    18. 18. Read Only Replicas
    19. 19. Secondary Replica – Active Log Sync Log Capture Network Log Recieve DB1 DB1 Log PoolCommit Redo Thread Log Cache Log Cache Redo PagesLog Flush Log Harden Page Updated DB1 Log DB1 Data Acknowledge DB1 Log Commit DB1 Data Secondary read is behind primary Log is first hardened and then applied Redo thread is asynchronous and runs in the background Latency (typically seconds) can be larger for log intensive operations like bulk import or index create/rebuild Sync Replica minimizes latency due to network issues
    20. 20. Auto-Stats on Readable Secondary Query Optimization and Statistics SQL Server uses cost based optimizer that heavily relies on object statistics If statistics are missing, SQL Server automatically creates them and persists Auto-stat on readable secondary will require physical Changes Example: Table T1 (C1, C2, C3) Query on primary with predicate (C3 > 10). SQL Server auto-create the statistics, if needed, on column C3 on primary replica Won‟t work on Readable Secondary as it will cause physical changes to the database. Similar issue if the statistical information is stale on the secondary replica. Solution Auto-create statistics on the secondary replica but persist them in TempDB Existing catalog views (e.g. sys.stats) show temporary statistics
    21. 21. Unplanned Disaster!
    22. 22. Availability Groups and Failover Cluster Instance  >
    23. 23. Coming up…Speaker Title Room Gruesome, Grotesque and Gory – Horrors Stories from theQuest Aintree World of ITIdera Tricks of the Trade - DBA tools Lancaster Data Replication Redefined – best practices for replicatingAttunity Empire data to SQL ServerFusion-io Myths and Monsters of Flash Derby Real Time and Historical Performance Troubleshooting withSQLSentry Pearce SQL Sentry #SQLBITS
    24. 24. Questions ?
    25. 25. AlwaysOn Resources“Denali” AlwaysOn Resource Center:http://msdn.microsoft.com/en-us/sqlserver/gg490638(en-us,MSDN.10) CTP download Documentation MSDN forums Microsoft Connect AlwaysOn Blog
    26. 26. Trace Flag 9532 TSQL featuresImportant – Trace Flag 9532Some Always On Availability Groups features require that the instances of SQLServer that host availability replicas have been enabled for trace flag 9532. Forinformation about which Transact-SQL options require enabling this trace flag, CREATE AVAILABILITY GROUP Transact-SQL options: Using more than two REPLICA ON clauses FAILURE_CONDITION_LEVEL HEALTH_CHECK_TIMEOUT SESSION_TIMEOUT Using any of the following ALTER AVAILABILITY GROUP Transact-SQL options: ADD REPLICA ON REMOVE REPLICA ADD DATABASE REMOVE DATABASE ENDPOINT_URL FAILURE_CONDITION_LEVEL HEALTH_CHECK_TIMEOUT SESSION_TIMEOUT
    27. 27. Thank You!

    ×