[5-day-delivery] Troubleshoot SQL Server Always On

Metadata

• Title: [5-day-delivery] Troubleshoot SQL Server Always On
• Category: 5-day-delivery
• Tag(s): SQL Server, Troubleshoot, Always On, Availability Groups
• Description: You want to troubleshoot and fix SQL Server Always On issues.

Common Issue(s)

• Setting up and configuring Always On Availability groups
• Problems configuring Always On Availability groups
• Issues with Listener configuration (19471, 19476 and other errors)
• Automatic Failover is not working as expected
• Issues connecting to Always On Availability groups
• Issues configuring Always On Availability groups in my Azure VM (IaaS)
• It takes a long time to failover from primary to secondary or vice-versa
• Changes on the Primary Replica are either not reflected on or slow to replicate to the Secondary Replica
• Manage the size of transaction log for AG databases
• Primary or Secondary Servers struck in Resolving State or you experience unexpected failovers
• Not able to bring resources online

Management

• Fixed-time: 5 working day(s)
• Fixed-scope:
  • 1 availability group (1-5 database) OR
  • 1-5 basic availability group
• Fixed-price: $500

Work Breakdown

• Troubleshoot Always On Availability Groups Configuration (SQL Server)
• Troubleshoot a Failed Add-File Operation (Always On Availability Groups)
• Troubleshoot automatic failover problems in SQL Server Always On environments
• Troubleshoot Availability group exceeded RTO
• Troubleshoot Potential data loss with asynchronous-commit availability-group replicas
• Troubleshoot High HADRSYNCCOMMIT wait type with Always On Availability Groups

Out of Scope

• Some solutions might require planning for a maintenance window and thus are out-of-scope for this task.

Deliverable(s)

• The availability groups should synchronize.
• Recommendations
  • Database Level
  • Server Level
• Clarification call (up to 1 hour)

Prerequisite(s)

• Database server access
• Screen sharing, if applicable