Download contained database authentication

Always On Availability Groups
INSTALLATION, SETUP & TUNING
Presenter
• René Romo González
• Primary DBA at Intel
• Trajectory
•
•
•
•
IT Intern at Milenio
IT Intern at Intel
Web & DB Administrator
Primary DBA
• Contact
•
[email protected]
Agenda
• Basic Concepts
• What is Always On Availability Group
• Terms and Definitions
• Benefits
• .Net Hotfixes that Support Availability Groups
• Windows System Requirements
• SQL Server Instance Requirements
• SQL Server Instance Restrictions
Agenda
• Availability Groups Restrictions
• Availability Databases Requirements
• Availability Databases Restrictions
• Backups
• Monitoring
• Links
Basic Concepts
• High Availability (HA) is about putting a set of technologies into
place before a failure occurs in order to prevent the failure from
affecting the availability of data.
• Disaster Recovery (DR) is about taking action after a failure occurs to
recovery any data lost and to make the data available again.
•
Recovery Time Objective (RTO) is the maximum allowable downtime when a failure occurs.
•
Recovery Point Objective (RPO) is the maximum allowable data-loss when a failure occurs.
What is Always On Availability Groups
The Always On Availability Groups feature is a high-availability and disaster-recovery solution.
Introduced in SQL Server 2012, Always On Availability Groups maximizes the availability of a set of
user databases for a company.
Important note: An availability group fails over at the level of an availability replica. Failovers are
not caused by database issues such as a database becoming suspect due to a loss of a data file,
deletion of a database, or corruption of a transaction log.
Terms and Definitions
• Availability Group
• Availability Database
• Primary Database
• Secondary Database
• Availability Replica
• Primary Replica
• Secondary Replica
• Availability Group Listener
Benefits
• Supports up to nine replicas
• Support alternative availability modes
•
Asynchronous-commit mode
•
Synchronous-commit mode. Important Note: Supports up to three replicas including primary one.
• Support several forms of Failovers
•
Automatic
•
Manual Failover
•
Manual Forced Failover
• Enables you to configure a given replica to support either or both of the following capabilities
•
Read Only connections
•
Performing Backup Operations
Benefits
• Supports automatic page repair for protection against page corruption
• Supports encryption and compression
• Provides Integrated set of tools to simplify deployment and management tasks
•
T-SQL
•
SSMS
•
AOAG Wizard
•
Add Database to AOAG Wizard
•
Add Replica AOAG Wizard
•
Failover AOAG Wizard
•
Dashboard
•
Object Explorer Details Pane
•
Powershell cmdlets
.Net Hotfixes that Support Availability Groups
Dependent Feature: SSRS
Description: Hotfix for .Net 3.5 SP1 adds support to SQL Client for Always On features of Readintent, readonly, and multisubnetfailover. The hotfix needs to be installed on each Reporting
Services report server.
KB 2654347: Hotfix for .Net 3.5 SP1 to add support for Always On features
Windows System Requirements
• System is not a Domain Controller
• Ensure that each computer is running Windows Server 2012 or later version
• Ensure that each computer is a node in a WSFC
• Ensure WSFC contains sufficient nodes to support your AOAG Configurations
 To administer a WSFC cluster, the user must be a system administrator on every cluster node
• SQL 2016 Introduces Distributed Availability Groups
SQL Server Instance Requirements
• Each instance must be running the Enterprise Edition
• All instances must use the same SQL Server Collation
• Enable Always On Availability Groups feature on each instance
• Each server instance requires a database mirroring endpoint
 If any DB that use FILESTREAM will be added to AOAG ensure it is enabled on every instance
 if any contained db will be added to AOAG ensure that contained database authentication
server option is set to 1.
 Requires CREATE ENDPOINT permission or membership in the sysadmin fixed server role. Also
requires CONTOL ON ENDPOINT.
 Requires membership in the Administrators group at OS Level.
SQL Server Instance Restrictions
• The cluster nodes of an FCI can host only one replica for a given availability group
• FCIs do not support automatic failover by availability groups
• Changing FCI network name
Availability Groups Restrictions
• Unique Availability Group Name. Important Note: 128 Characters as max length
• Each Group supports one primary replica and up to eight
• Maximum number of Availability Groups and Availability database per computer
• Do not use Failover Cluster Manager to manipulate availability groups
Task
Required Permissions
Creating an availability group
Requires membership in the sysadmin fixed server role and either CREATE AVAILABILITY
GROUP server permission, ALTER ANY AVAILABILITY GROUP permission, or CONTROL
SERVER permission.
Altering an availability group
Requires ALTER AVAILABILITY GROUP permission on the availability group, CONTROL
AVAILABILITY GROUP permission, ALTER ANY AVAILABILITY GROUP permission, or
CONTROL SERVER permission.
In addition, joining a database to an availability group requires membership in
the db_owner fixed database role.
Dropping/deleting an availability group
Requires ALTER AVAILABILITY GROUP permission on the availability group, CONTROL
AVAILABILITY GROUP permission, ALTER ANY AVAILABILITY GROUP permission, or
CONTROL SERVER permission. To drop an availability group that is not hosted on the local
replica location you need CONTROL SERVER permission or CONTROL permission on that
Availability Group.
Availability Databases Requirements
• Be a User Database
• Reside on the instance where you create the availability group
• Be a read-write Database
• Be a multi-user Database
• Not use AUTO_CLOSE
• User Full Recovery Mode
• Possess at least one full database backup
• Not belong to any existing availability group
• Not be configured for database mirroring
Availability Databases Restrictions
If the file path (including the drive letter) of a secondary database differs from the path of the
corresponding primary database, the following restrictions apply:
•
•
•
New Availability Group Wizard/Add Database to Availability Group Wizard: The Full option is
not supported
RESTORE WITH MOVE
Impact on add-file operations: A later add-file operation on the primary replica might fail on
the secondary databases. This failure could cause the secondary databases to be suspended.
This, in turn, causes the secondary replicas to enter the NOT SYNCHRONIZING state.
Backups
Monitoring
• System Center Monitoring Pack for SQL Server
• T-SQL
sys.dm_hadr_auto_page_repair
• SSMS
sys.dm_hadr_availability_group_states sys.dm_hadr_database_replica_cluster_states
• System Monitor
sys.dm_hadr_availability_replica_clust sys.dm_hadr_database_replica_states
er_nodes
sys.dm_hadr_cluster_networks
sys.dm_hadr_availability_replica_clust sys.dm_hadr_instance_node_map
er_states
sys.dm_hadr_availability_replica_state sys.dm_hadr_name_id_map
s
sys.dm_hadr_cluster
sys.dm_hadr_cluster_members
sys.dm_tcp_listener_states
Links
• https://msdn.microsoft.com/en-us/library/hh510230.aspx
• https://msdn.microsoft.com/en-us/library/ff878487.aspx
• https://msdn.microsoft.com/en-us/library/mt651673.aspx
• https://msdn.microsoft.com/en-us/library/ff877954.aspx
• https://msdn.microsoft.com/en-us/library/ff877943.aspx
Q&A