Troubleshooting Internal Load Balancer Listener Connectivity in Azure

Problem Unable to Connect to Azure availability group listener Creating an availability group in order to make your application highly available when running on Azure virtual machines (IaaS) is very popular. The availability group listener requires special configuration steps in Azure as opposed to running on premise.  For more information on step by step configuration…


How to Apply Transaction Logs to Secondary When it is Far Behind

  Problem Large Send Queue You discover that the log send queue for a given availability database has grown very large, which threatens your Recovery Point Objective (RPO) and the transaction log has grown very large on the primary replica, possibly threatening to fill the drive. The cause may have been for various reasons: you…


Making Service Broker Application Highly Available With AlwaysOn

  If you have a Service Broker (SSB) application connecting to SQL Server using an AlwaysOn availability group listener, in the event of an unexpected failover, some messages may be lost or stuck in the transmission queue on the old primary (new secondary) after the failover. This could be an automatic failover or manual failover…


AlwaysOn Readable Secondaries Can Display Misleading Data & Log File Paths

Written By: Grant Carter, Senior Premier Field Engineer Reviewed By: Mark Weber – Principal Premier Field Engineer Norm Eberly – Senior Premier Field Engineer Charles Allard – Senior Premier Field Engineer Nick Schueler – Senior Premier Field Engineer Curt Matthews – Senior Escalation Engineer   Problem You may discover on a readable secondary database that is…


SQL Server 2016 AlwaysOn Availability Group Enhancements: Support for Encrypted Databases

Overview In SQL Server 2012 and SQL Server 2014, encrypted databases could be added to an AlwaysOn availability group, but they could not be added using the New Availability Group wizard. Additionally, in the event of a failover, the encrypted database data could not be accessed. This is because the database master key in the…


SQL Server 2016 AlwaysOn Availability Group Enhancements: Multiple Automatic Failover Targets

Overview SQL Server 2104 and SQL Server 2012 can have two synchronous secondary replicas. One synchronous secondary replica can serve the role as automatic failover partner with the primary replica. In SQL Server 2016 both synchronous secondary replicas can be configured as automatic failover partners with the primary replica. Benefits This will allow following benefits This increases the chances…


SQL Server 2016 AlwaysOn Availability Group Enhancements: Load Balance Read-Only Routing

Overview SQL Server 2104 and SQL 2012 read-only routing directed traffic to the first available replica in the routing list, unless it was not accessible, and then it would direct the connection to the next replica in the routing list. When you have multiple secondary replicas available for read, it is not possible to spread…


SQL Server 2016 AlwaysOn Availability Group Enhancements: Initial Data Synchronization Without Database and Log Backup

Overview In SQL Server 2012 and 2014, initializing a secondary replica is cumbersome to do manually, and requires backup and restore of your database and transaction log from the primary to a network share, and then a restore of the database and log backup files to the secondary replica. The availability group wizard can automate…


SQL Server 2016 AlwaysOn Availability Group Enhancements: Basic Availability Group on Standard Edition

Basic Availability Group on Standard Edition Historically, SQL Server database mirroring offered high availability of a SQL Server database. AlwaysOn availability groups has supplanted database mirroring as the future of high availability in SQL Server, meanwhile, database mirroring has been marked for deprecation. As database mirroring is deprecated, SQL Server 2016 introduces AlwaysOn Basic Availability…


Improved AlwaysOn Availability Group Lease Timeout Diagnostics

When your AlwaysOn availability group is configured for automatic failover, you may find your availability group failed over, or if configured for manual failover, you may observe your availability group transition from the PRIMARY role to the RESOLVING role, during which users cannot access the availability group databases. Checking the SQL Server error log, you…