Clik here to view.
Enhance AlwaysOn Failover Policy to Test SQL Server Database Data and Log Drives
In SQL Server 2012 and 2014, AlwaysOn health diagnostics detect the health of the SQL Server process in several ways. However, no health detection is performed on the accessibility or viability of the...
View ArticleClik here to view.
Troubleshooting Availability Group Listener in Azure
Configuring an availability group listener in Azure is much more complex than doing it on-premises, due to the some limitations of Azure networking. This topic helps you troubleshoot your availability...
View ArticleClik here to view.
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 manual, you may observe your...
View ArticleClik here to view.
SQL Server 2016 AlwaysOn Availability Group Enhancements: Basic Availability...
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...
View ArticleClik here to view.
SQL Server 2016 AlwaysOn Availability Group Enhancements: Initial Data...
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...
View ArticleClik here to view.
SQL Server 2016 AlwaysOn Availability Group Enhancements: Load Balance...
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...
View ArticleClik here to view.
SQL Server 2016 AlwaysOn Availability Group Enhancements: Multiple Automatic...
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...
View ArticleClik here to view.
SQL Server 2016 AlwaysOn Availability Group Enhancements: Support for...
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,...
View ArticleAlwaysOn 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...
View ArticleClik here to view.
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...
View ArticleClik here to view.
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...
View ArticleClik here to view.
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...
View ArticleAvoid Availability Group Database Data Loss: Do not Deploy File Share Witness...
Cluster Quorum File Share Witness Should Not be Part of a DFS Namespace When deploying AlwaysOn availability groups you may decide to add a vote to Windows Cluster quorum by configuring a File Share...
View ArticleClik here to view.
Availability Group Database Reports Not Synchronizing / Recovery Pending...
You may find that one or more availability group databases is reported ‘Not Synchronizing / Recovery Pending’ on the primary replica or ‘Not Synchronizing’ on one of the secondary replicas. Despite...
View ArticleClik here to view.
Availability Group Database Reports Not Synchronizing / Recovery Pending...
 You may find that one or more availability group databases is reported ‘Not Synchronizing / Recovery Pending’ on the primary replica or ‘Not Synchronizing’ on one of the secondary replicas. Despite...
View ArticleClik here to view.
Analyze Network Latency Impact on Remote Availability Group Replica
Multisite availability groups allow customers to deploy copies of business data across multiple sites, for disaster recovery and/or for reporting purposes, offering near real-time changes available to...
View ArticleClik here to view.
Analyze Synchronous Commit Impact on High Commit Rate Workloads
Workloads that rely on auto-commit (each operation like an INSERT has an implied, corresponding begin and commit transaction) and perform a large number of small transactions may take significantly...
View Article