SYED SAJID WASIM SQL SERVER ALWAYS ON Step by Step.

Slides:



Advertisements
Similar presentations
Todays Goal – AlwaysOn in 60 Minutes Where well start:
Advertisements

SQL Server AlwaysOn: Active Secondaries Luis Vargas Program Manager Microsoft Corporation DBI312.
Implementing SQLServer AlwaysON Sarabpreet Singh Anand SQL Server – MVP SQLServerGeeks.com (VP)
SharePoint 2013 & SQL Server 2012 Availability Groups The Rough Guide.
Mecanismos de alta disponibilidad con Microsoft SQL Server 2008 Por: ISC Lenin López Fernández de Lara.
Virtual techdays INDIA │ September 2011 High Availability - A Story from Past to Future Balmukund Lakhani │ Technical Lead – SQL Support, Microsoft.
Chapter 10 : Designing a SQL Server 2005 Solution for High Availability MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design.
Architecting Availability Groups
SQL-Server 2012 Always On.
Maintaining a Mirrored Database Tips and Tricks by Paul G. Hiles.
MODIFY THIS SLIDE FOR ACTUAL PRESENTER, DELETE THIS BAR AFTER MODIFICATION.
SQLintersection Session SQL37 SQL Server 2012 Availability Groups Aaron Bertrand
Unified solution Easy to configure, manage, and monitor Reuse existing investments SAN/DAS environments Allow using HA hardware resources Fast seamless.
SQL2005 Cluster Build. IP Request Request 6 IP Addresses – One for EACH SQL virtual server (2) – One for the cluster – One for Distributed Transaction.
SQLCAT: SQL Server HA and DR Design Patterns, Architectures, and Best Practices Using Microsoft SQL Server 2012 AlwaysOn Sanjay Mishra Program Manager.
7. Replication & HA Objectives –Understand Replication and HA Contents –Standby server –Failover clustering –Virtual server –Cluster –Replication Practicals.
Speaker Name 00/00/2013. Solution Requirements.
Alwayson Availability Groups
Course Topics Administering SQL Server 2012 Jump Start 01 | Install and Configure SQL Server04 | Manage Data 02 | Maintain Instances and Databases05 |
Data Disaster Recovery Planning Greg Fibiger 1/7/2016.
1 Chapter Overview Using Standby Servers Using Failover Clustering.
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.
Narasimha Reddy Gopu Jisha J. Agenda Introduction to AlwaysOn * AlwaysOn Availability Groups (AG) & Listener * AlwaysOn Failover * AlwaysOn Active Secondaries.
Deploying Highly Available SQL Server in Windows Azure A Presentation and Demonstration by Microsoft Cluster MVP David Bermingham.
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.
What HADR Option(s) Are Right For You?. Where’s The AlwaysOn?
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.
William Durkin A Gourmet Menu of SQL Server High Availability Options.
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.
ALWAYSON AVAILABILITY GROUPS Replicas, Listeners & Quorums, Oh My! Kevin Howell SQL Saturday #517 Philadelphia, June 2016.
Architecting Enterprise Workloads on AWS Mike Pfeiffer.
SQLSaturday (Silicon Valley) – Mar
Sponsors.
Welcome to SharePoint Saturday Houston
Database Mirroring with SQL Server
SQL Server 2012 AlwaysOn and SQLSentry
ALWAYSON AVAILABILITY GROUPS
Navigating the options for Data Redundancy
Disaster Recovery Where to Begin
AlwaysOn Mirroring, Clustering
A Technical Overview of Microsoft® SQL Server™ 2005 High Availability Beta 2 Matthew Stephen IT Pro Evangelist (SQL Server)
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.
VceTests VCE Test Dumps
Windows Azure Migrating SQL Server Workloads
VIDIZMO Deployment Options
Design and Implement Cloud Data Platform Solutions
Contained DB? Did it do something wrong?
Configuring the network environment
SQL AlwaysOn Availability Groups
Required 9s and data protection: introduction to sql server 2012 alwayson, new high availability solution Santosh Balasubramanian Senior Program Manager.
AlwaysOn, an Early bird Overview
AlwaysOn Availability Groups 101
Disaster Recovery Where to Begin
Oracle Architecture Overview
What’s new in SQL Server 2016 Availability Groups
SQL Server on Linux: High Availability And Disaster Recovery
Database Mirroring The Basics
AlwaysOn Availability Groups
High Availability/Disaster Recovery Solution
Distributed Availability Groups
04 | Always On High Availability
Distributed Availability Groups Praveen Kumar. What we will cover Availability group refresher The HA/DR solution Distributed availability groups – what.
SQL AlwaysOn Availability Groups
Designing Database Solutions for SQL Server
Presentation transcript:

SYED SAJID WASIM SQL SERVER ALWAYS ON Step by Step

SYED SAJID WASIM Manager ADC, DHAKABANK Limited Focused on database and development technologies MCT, MCSE, MCTS on Data Platform 18 Years IT Industry Experience Working with SQL Server since version 6.5 www.Linkedin.com/in/SajidWasim

What is SQL Server AlwaysOn? Introduced in SQL Server 2012 Requires SQL Server Standard/Enterprise Edition SQL Server AlwaysOn describes two distinct SQL Server High Availability features: AlwaysOn Availability Groups AlwaysOn Failover Cluster Instance

Why SQL Server AlwaysOn? Feature Database Mirroring AlwaysOn AG Maximum number of secondary databases 1 Mirror 8 Secondaries Requires Windows Clustering No Yes, however the SQL Servers can be stand-alone Automatic failover Yes, requires witness server and high-safety mode Yes, one HA or DR Choose one Each secondary independently configurable Groups of databases No, each database is configured separately Multiple databases can be grouped to failover together Can be used for reporting Only against a database snapshot of the  mirror Yes Offload backups Connection to active database Requires special connection string for failover Redirection handled by Windows Clustering with a virtual name. Special connection string not required Connection string to mirror or secondary database N/A Can be configured with an Application Intent connection string to automatically redirect or can use traditional connection string with server name. Why SQL Server AlwaysOn?

FEATURES Grouping Databases into Failover Groups Integration with Windows Server Failover Clustering (WSFC) Uses WSFC quorum models Uses Cluster Client Access Point Important features Database Health causing failovers Support for Distributed Transaction Coordinator Synchronous replicas Optimized log transport Load balancing

Business Intelligence High Availability features for SQL Server 2016 Licenses: Feature Name Enterprise Business Intelligence Standard Web Express Server Core support Yes Log Shipping   Database mirroring Yes (Safety Full Only) Witness only Backup compression Alwayson Failover Cluster Instances Yes (Node support: Operating system maximum Yes (Node support: 2) AlwaysOn Availability Groups Yes (up to 8 secondary replicas, including 2 synchronous secondary replicas) …

AlwaysOn Requirements System Setup Use Server Manager to install the Failover Clustering feature on all nodes. Use the Failover Cluster Management tool to create a new Windows failover cluster. Install a new standalone instance of SQL Server on each cluster node.

AlwaysOn Requirements Database Setup Availability groups must be created with user databases. Systems databases can't be used. Databases must be read-write. Read-only databases aren't supported. Databases must be multiuser databases. Databases can't use the AUTO_CLOSE feature. Databases must use the full recovery model, and there must be a full backup of them. A given database can only be in a single availability group, and that database can't be configured to use database mirroring.

Steps Configuring AlwaysOn Availability Groups Install Windows Cluster Install a Standalone SQL Server 2012 Use the domain account for the SQL service account Open Port 1433 and 5022 or disable the Windows Firewall Create a sample database Set recovery model to Full Back up this sample database Enable the AlwaysOn feature on both instances using SQL Server Configuration Manager Create an Availability Group using the Availability Group Wizard

DEMO

Resources Always On Overview http://msdn.microsoft.com/en-us/library/ms189134.aspx http://www.tech-coffee.net/alwayson-availability-group-introduction https://channel9.msdn.com/posts/SQL11UPD01-REC-07 Understanding Quorum in a Failover Cluster http://blogs.msdn.com/b/clustering/archive/2011/05/27/10169261.aspx Understanding File Share Witness Placement http://blogs.technet.com/b/askpfeplat/archive/2012/06/27/clustering-what-exactly-is-a-file-share-witness-and-when-should-i-use-one.aspx Configuring Availability Groups http://blogs.technet.com/b/scvmm/archive/2012/10/24/how-to-configure-sql-2012-alwayson-availability-groups-in-system-center-2012-virtual-machine-manager-service-pack-1.aspx http://www.brentozar.com/archive/2011/07/how-set-up-sql-server-denali-availability-groups/ What’s New in Failover Clustering in Windows Server 2012 R2 http://technet.microsoft.com/en-us/library/dn265972.aspx

Q&A SQL SERVER 2016 What’s Your Message?