1. IT Pro Day SQL Server 2012 AllwaysOn Stephan Hurni Microsoft V-TSP Principal Consultant, Trivadis AG stephan.hurni@trivadis.com

2. IT Pro Day Trivadis solution portfolio and competences IT SOLUTIONS, SERVICES & PRODUCTS TECHNOLOGIES Microsoft, Oracle, IBM, Open Source Integration, Application Performance Management, Security Infrastructure Engineering Application Development Business Intelligence Business Integration Services Training Managed Services

3. IT Pro Day Trivadis facts & figures 11 Trivadis locations with more than 600 employees Financially independent and sustainably profitable Key figures 2011  Revenue CHF 104 / EUR 84 Mio.  Services for more than 800 clients in over 1,900 projects  200 Service Level Agreements  More than 4,000 training participants  Research and development budget: CHF 5.0 / EUR 4 Mio.

4. HADR HA Enhancements in SQL Server 2012

5. Failover Clustering Virtual Networkname (transparent)Multidatabase failoverShared storage neededNo active secondaries available DR only with Storage Replication or Logshipping/ Database Mirroring Database Mirroring Fast FailoverNo Shared Storage needed Application has to be “mirroring-aware” (SNAC or connectstring modification) No virtual network name to connect Only 1 active secondary with database snapshots on the mirror Log Shipping Multiple SecondariesNo Shared Storage neededNeeds good monitoringNo automatic failover Secondaries offline while applying transactionlog backups

6. Failover Clustering Virtual Networkname (transparent)Multidatabase failoverShared storage neededNo active secondaries available DR only with Storage Replication or Logshipping/ Database Mirroring Database Mirroring Fast FailoverNo Shared Storage needed Application has to be “mirroring-aware” (SNAC or connectstring modification) No virtual network name to connect Only 1 active secondary with database snapshots on the mirror Log Shipping Multiple SecondariesNo Shared Storage neededNeeds good monitoringNo automatic failover Secondaries offline while applying transactionlog backups

7. AlwaysOn Availability Groups is a new feature that enhances and combines failover cluster, database mirroring and log shipping capabilities Multi-database failover Multiple secondaries Total of 4 secondaries 2 synchronous secondaries 1 automatic failover pair Synchronous and asynchronous data movement Built in compression and encryption Flexible failover policy Automatic Page Repair Application failover using virtual name Configuration Wizard Dashboard System Center Integration Rich diagnostic infrastructure File-stream replication Replication publisher failover Flexible Integrated Efficient Active Secondary Readable Secondary Backup from Secondary Automation using power-shell

8. AlwaysOn Availability Groups is a new feature that enhances and combines failover cluster, database mirroring and log shipping capabilities Multi-database failover Multiple secondaries Total of 4 secondaries 2 synchronous secondaries 1 automatic failover pair Synchronous and asynchronous data movement Built in compression and encryption Flexible failover policy Automatic Page Repair Application failover using virtual name Configuration Wizard Dashboard System Center Integration Rich diagnostic infrastructure File-stream replication Replication publisher failover Flexible Integrated Efficient Active Secondary Readable Secondary Backup from Secondary Automation using power-shell

9.  Based on Windows Server Failover Cluster  Conjunction of multiple Database Mirrors with Failover Clustering

10. Synchronous Data Movement Asynchcronous Data Movement AG Example Primary in Calgary Failover Partner in Vancouver Sync DR in Toronto Async Secondary in Montreal (Reporting) Async Secondary in London (Geo DR)

11.  Availability Databases DBs can be added to availability groups as primary  Availability Replicas | primary DBs can have up to 4 replicas  Availability Modes Asynchronous-commit mode Synchronous-commit mode (max. 2 secondaries)  Types of Failover ¦ planned manual, automatic  Client Connections to VNN (virtual network name) (group listener with unique DNS A-record + multiple C-Names)  Automatic Page Repair

12.  Built-in as feature in Windows since 2003  Check Server Requirements http://msdn.microsoft.com/en-us/library/ff878487(v=sql.110).aspx http://msdn.microsoft.com/en-us/library/ff878487(v=sql.110).aspx  Create Windows Cluster

13.  Creator (cluster computer account in ADS) of AGs must have rights in ADS  join computers  local administrative rights on nodes  Have Network Name, IP Address, Connection Port, min 1 Database, Listener Port and account for Availability Group ready each AG has: own NN, IP Address, Connection Port  Create multiple AGs for performance benefits  min 1 AG per Node (active processes per Node)  approximately 40MB/sec throughput per AG  Combine multiple DBs belonging together to same AGs

14. CREATE AVAILABILITY GROUP group_name WITH ( [,...n ] ) FOR [ DATABASE database_name [,...n ] ] REPLICA ON [,...n ] [ LISTENER ‘dns_name’ ( ) ] [ ; ] ::= AUTOMATED_BACKUP_PREFERENCE = { PRIMARY | SECONDARY_ONLY| SECONDARY | NONE } | FAILURE_CONDITION_LEVEL = { 1 | 2 | 3 | 4 | 5 } | HEALTH_CHECK_TIMEOUT = milliseconds ::= WITH ( ENDPOINT_URL = 'TCP://system-address:port', AVAILABILITY_MODE = { SYNCHRONOUS_COMMIT | ASYNCHRONOUS_COMMIT }, FAILOVER_MODE = { AUTOMATIC | MANUAL } [, [,...n ] ] ) ::= BACKUP_PRIORITY = n | SECONDARY_ROLE ( { [ ALLOW_CONNECTIONS = { NO | READ_ONLY | ALL } ] [,] [ READ_ONLY_ROUTING_URL = 'TCP://system-address:port' ] } ) | PRIMARY_ROLE ( { [ ALLOW_CONNECTIONS = { READ_WRITE | ALL } ] [,] [ READ_ONLY_ROUTING_LIST = { ( ‘ ’ [,...n ] ) | NONE } ] } ) | SESSION_TIMEOUT = integer ::= { WITH DHCP [ ON ( ) ] | WITH IP ( { ( ) } [,...n ] ) [, PORT = listener_port ] } ::= ‘four_part_ipv4_address’, ‘four_part_ipv4_mask’ ::= { ‘four_part_ipv4_address’, ‘four_part_ipv4_mask’ | ‘ipv6_address’ } http://technet.microsoft.com/de-de/library/ff878399.aspx (CREATE AVAILABILITY GROUP (Transact-SQL)

15. ALTER AVAILABILITY GROUP AV01 SET (FAILURE_CONDITION_LEVEL = 1) ALTER AVAILABILITY GROUP AG1 SET (HEALTH_CHECK_TIMEOUT = 60000)

16. select * from sys.dm_hadr_availability_group_states select * from sys.dm_hadr_availability_replica_cluster_nodes select * from sys.dm_hadr_availability_replica_cluster_states select * from sys.dm_hadr_availability_replica_states select * from sys.dm_hadr_cluster select * from sys.dm_hadr_cluster_members select * from sys.dm_hadr_cluster_networks select * from sys.dm_hadr_database_replica_cluster_states select * from sys.dm_hadr_database_replica_states select * from sys.dm_hadr_instance_node_map select * from sys.dm_hadr_name_id_map select * from sys.dm_hadr_auto_page_repair select routing_priority, read_only_routing_url, replica_server_name, endpoint_url from sys.availability_read_only_routing_lists A join sys.availability_replicas B on A.replica_id = b.replica_id

17. Demo Availability Groups

19.  Read_only with Database Mirroring?  Read_only with HADR Availability Groups Secondaries are readable but not updateable  Routing List  SQLcmd  with SSMS DB context -E –S AV01 -K ReadOnly -d AV -Q [Query] ApplicationIntent=ReadOnly

20.  Save Network bandwith for redundant Full Backups  copy_only for Full Backups  Take care of backup location for TXLog Backups  TXlog-chain!!!  HADR backup perferences select sys.fn_hadr_backup_is_preferred_replica ('AV')

21. Demo Read-only secondaries Backup secondaries

22.  Have a solid standardized and automated Maintenance in place  think of failover situations  Beware of new Databases behaviors in AGs  read_only  Backup secondaries  Optimize/Change your Database Maintenance Jobs  ask Trivadis how to Maintain SQL Server Databases and deserve more

23. Questions SQL Server 2012 HADR

24. Am Trivadis Stand Signed by Thomas Huber 1. Preis 2. Preis 3. Preis Wettbewerb