Example of a page header

Slides:



Advertisements
Similar presentations
Implementing SQLServer AlwaysON Sarabpreet Singh Anand SQL Server – MVP SQLServerGeeks.com (VP)
Advertisements

SharePoint 2013 & SQL Server 2012 Availability Groups The Rough Guide.
0 SQL Server AlwaysOn – SharePoint 2013 High Availability and Disaster Recovery Sal Bawany, Solutions Architect
Database Optimization & Maintenance Tim Richard ECM Training Conference#dbwestECM Agenda SQL Configuration OnBase DB Planning Backups Integrity.
SharePoint and SQL Server integration Demo: SQL Server Optimizing Configurations SQL Server 2014 for SharePoint 2013 Avoiding ginormous transaction.
SharePoint Business Continuity Management with SQL Server AlwaysOn
Maintaining a Mirrored Database Tips and Tricks by Paul G. Hiles.
SQLintersection Session SQL37 SQL Server 2012 Availability Groups Aaron Bertrand
Module 10: Maintaining High-Availability. Overview Introduction to Availability Increasing Availability Using Failover Clustering Standby Servers and.
Speaker Name 00/00/2013. Solution Requirements.
Alwayson Availability Groups
Narasimha Reddy Gopu Jisha J. Agenda Introduction to AlwaysOn * AlwaysOn Availability Groups (AG) & Listener * AlwaysOn Failover * AlwaysOn Active Secondaries.
SQL Server 2014 AlwaysOn Step-by-Step SQL Server 2014 AlwaysOn Step-by-Step A hands on look at implementing AlwaysOn in SQL Server 2014.
SQL Server High Availability Introduction to SQL Server high availability solutions.
All the things you need to know before setting up AlwaysOn Michael Steineke SQL & BI Solution Lead Enterprise Architect Concurrency, Inc.
Windows Server Failover Clustering (WSFC) with SQL Server.
Architecting Availability Groups An analysis of Microsoft SQL Server Always-On Availability Group architectures 1.
You Inherited a Database Now What? What you should immediately check and start monitoring for. Tim Radney, Senior DBA for a top 40 US Bank President of.
AlwaysOn In SQL Server 2012 Fadi Abdulwahab – SharePoint Administrator - 4/2013
FUN WITH AVAILABILITY GROUPS Christopher Wolff SQL Server Database Engineer, Xero.
Redmond Protocols Plugfest 2016 Kevin Farlee Senior Program Manager SQL Server AlwaysOn in SQL Server 2016.
Architecting Availability Groups An analysis of Microsoft SQL Server Always-On Availability Group architectures 1.
SQL 2012 – Always On Deep Dive Bob Duffy Database Architect Prodata SQL Centre of Excellence 11 th April 2013.
ALWAYSON AVAILABILITY GROUPS Replicas, Listeners & Quorums, Oh My! Kevin Howell SQL Saturday #517 Philadelphia, June 2016.
You Inherited a Database Now What?
Welcome to SharePoint Saturday Houston
Reporting Services In An AlwaysOn World
SQL Replication for RCSQL 4.5
Architecting Availability Groups
ALWAYSON AVAILABILITY GROUPS
Navigating the options for Data Redundancy
Disaster Recovery Where to Begin
AlwaysOn Mirroring, Clustering
Maximum Availability Architecture Enterprise Technology Centre.
Transactional replication
Always On Multi-Site Patterns
Always On Availability Groups
Always on HA SQL Server Always ON feature is the new comprehensive high availability and disaster recovery solution which increases application availability.
Contained DB? Did it do something wrong?
Always On : Multi-site patterns
AlwaysOn Availability Groups 101
Tips for SQL Server Performance and Resiliency
Tips for SQL Server Performance and Resiliency
Introduction to Clustering
Disaster Recovery Where to Begin
Architecting Availability Groups
How to keep your database servers out of the news Matt Gordon
Re-Indexing - The quest of ultimate automation
Always On : Multi-site patterns
What’s new in SQL Server 2016 Availability Groups
Planning High Availability and Disaster Recovery
Always On : Multi-site patterns
SpiraTest/Plan/Team Deployment Considerations
SYED SAJID WASIM SQL SERVER ALWAYS ON Step by Step.
SQL Server on Linux: High Availability And Disaster Recovery
Distributed Availability Groups
AlwaysOn Availability Groups
You Inherited a Database Now What?
High Availability/Disaster Recovery Solution
Top 5 TIPS TO KEEP Always on AGs humming and users happy
Distributed Availability Groups
Speaker info Matt Gordon Architect
Top 5 TIPS TO KEEP Always on AGs humming and users happy
04 | Always On High Availability
Distributed Availability Groups
Distributed Availability Groups Praveen Kumar. What we will cover Availability group refresher The HA/DR solution Distributed availability groups – what.
Top 5 TIPS TO KEEP Always on AGs humming and users happy
SQL AlwaysOn Availability Groups
Designing Database Solutions for SQL Server
The DBA Quit and now you’re it:
Presentation transcript:

Example of a page header Top 5 Tips to Keep AlwaysOn Always Humming and Users Happy

Thank you to our Gold Sponsors #531| Louisville 2016 Thank you to our Gold Sponsors

Thank you to our Silver Sponsors #531| Louisville 2016 Thank you to our Silver Sponsors Thank you to our Bronze Sponsors

Example of a page header SPEAKER INFO Matt Gordon Senior Consultant mgordon@pragmaticworks.com @sqlatspeed www.sqlatspeed.com

How I Picked My Twitter Handle and Domain Name ABOUT ME How I Picked My Twitter Handle and Domain Name

INTRODUCTORY QUESTIONS What Do We Know About Availability Groups? Who is responsible for administering an Always On AG? Who thinks they will be responsible for that in the near future? If you are responsible for an AG, is it in production? If so, do you have AGs only in production?

What are we going to talk about today? Agenda Quorum Design Read-only Routing Lists Users and Logins Backup Strategies Maintenance Strategies

Your Vote Counts! What is cluster quorum? Why is it important? Quorum votes Your Vote Counts! What is cluster quorum? How the cluster monitors its health Why is it important? Cluster will be set offline is quorum is absent Availability group listener is a cluster resource AG will be inaccessible if quorum is lost Who decides on the design? Should be collaborative between DBA and ops DBA should understand design

Your Vote Counts! Quorum Modes Node Majority Quorum votes Your Vote Counts! Quorum Modes Node Majority Recommended if you have an odd number of voting nodes Node and File Share Majority Recommended if you have an even number of voting nodes and multi-site cluster Also recommended if you have an even number of voting nodes and no shared storage Node and Disk Majority Requires shared disk cluster resource Recommended for even number of nodes but no multi-site Disk Only

Read-only routing lists Distributing The Workload What is a read-only routing list? Directs read-only connections to readable secondaries Configured per availability group node Not load-balancing mechanism until SQL Server 2016 What is required to setup a read-only routing list? AG must have a listener One or more replicas must be readable secondaries

Accessible and Available Data Copy User Logins Accessible and Available Data SQL Server security objects Users at database level Logins at instance level Users Will be a part of each replica database No additional setup required Logins Will need to be recreated for each instance Sp_help_revlogin makes this much easier

Keeping Logins Consistent Across AGs

Regular transaction log backups Backups To Help The Database Keep Up Transaction log backup strategy Depends on database workload Important to regulate transaction log size “Do something, even if it’s wrong” Monitor your backups Improve recovery time Minimize use of storage resources Avoid the dreaded shrinking operations

Stagger index maintenance Slow Down To Speed Up Regular index maintenance If you are not doing this, you should be Strategy depends on workload Reorganize operations generate more log traffic than rebuilds Effect on replicas Large operations can generate lots of log traffic Log data must be transported to/restored at replica

Stagger index maintenance Do’s and Don’ts Staggering do’s and don’ts DO ensure that all large indexes are not being rebuilt at nearly the same time DO closely monitor the lag between primary and replicas when first implementing index maintenance DO NOT reorganize every index each day at the same time lest your network look like the picture

Checking AG Replica Lag

Checking AG Replica Lag STAGGER MAINTENANCE Checking AG Replica Lag select SYSDATETIME(), arcs.replica_server_name, drcs.database_name, drs.synchronization_state_desc, ars.synchronization_health_desc, CASE WHEN drcs.is_failover_ready=0 THEN 'Possible Data Loss' WHEN drcs.is_failover_ready=1 THEN 'No Data Loss' END as is_failover_ready, ISNULL(convert(varchar,drs.log_send_queue_size,113),'Is Current Primary') log_send_queue_size, ISNULL(convert(varchar,drs.last_sent_time,113),'Is Current Primary') last_sent_time, ISNULL(convert(varchar,drs.last_received_time,113),'Is Current Primary') last_received_time, drs.last_commit_lsn, drs.last_commit_time, drs.last_hardened_lsn, ISNULL(convert(varchar,drs.last_hardened_time,113),'Is Current Primary') last_hardened_time, ISNULL(convert(varchar,drs.last_sent_lsn,113),'Is Current Primary') last_sent_lsn, ISNULL(convert(varchar,drs.last_received_lsn,113),'Is Current Primary') last_received_lsn, ISNULL(convert(varchar,drs.redo_rate,113),'Is Current Primary') redo_rate, ISNULL(convert(varchar,drs.redo_queue_size,113),'Is Current Primary') redo_queue_size, ars.role_desc from sys.dm_hadr_availability_replica_states ars join sys.dm_hadr_database_replica_states drs on ars.replica_id = drs.replica_id join sys.dm_hadr_database_replica_cluster_states drcs on drs.group_database_id = drcs.group_database_id and drs.replica_id=drcs.replica_id join sys.dm_hadr_availability_replica_cluster_states arcs on drcs.replica_id=arcs.replica_id order by arcs.replica_server_name, drcs.database_name;

Example of a page header SPEAKER INFO Matt Gordon Senior Consultant mgordon@pragmaticworks.com @sqlatspeed www.sqlatspeed.com