20 Questions to Ask About Your Availability Group Design

Questions about the overall project:

  1. What are your RPO and RTO goals?
  2. Are there financial penalties if we miss the goals? (Like contracts, refunds to customers, etc)
  3. Does this app have regularly scheduled maintenance windows, or is it 24/7?
  4. What’s the ballpark size of the data today? In 3 years?

Questions about the team:

  1. How many DBAs do we have? How many sysadmins?
  2. Have they managed Windows clusters before? Multi-subnet clusters?
  3. Do they have PowerShell experience?
  4. How do we handle Windows and SQL patches?
  5. What’s the current on call rotation? Are the skills spread evenly through the rotation, or do SQL cluster calls always require one person to wake up?

Questions about the apps:

  1. Do the apps require cross database transactions?
  2. Do all databases have to be at the same exact point in time when failing over to an async (DR) replica, or is it okay if some databases have more data loss than others?
  3. What apps are going to be querying the secondary?
  4. How much hardware horsepower do we use on the existing SQL Servers?
  5. Are users currently happy with performance?
  6. If the secondary’s data is delayed (minutes, hours), is there a financial risk? (If replication breaks, how urgent is it that we fix it?)

Questions about the hardware and licensing:

  1. What licensing do we have already? SA?
  2. What SQL Server version are we aiming for?
  3. Are we deploying on new hardware/VMs, or trying to reuse existing ones?
  4. Why not the cloud?
  5. Why AGs, and why not log shipping, failover clusters, database mirroring, etc.?
Previous Post
When Does SARGability Matter Most?
Next Post
Thoughts About the 2019 Salary Survey’s New Questions

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.