Adding Managed Instances to SQL Server Distributed Availability Groups

SQL Server Always On Availability Groups help you build a more highly available database server by spanning your database across two or more SQL Server instances. When the primary goes down, the secondary can take over. You can also scale out reads to the secondary servers. Distributed Availability Groups take this a step further and…
Read More

[Video] Installing SQL Server Updates in an Availability Group, and Save 50% on Training

This week, we’re sharing Instant Replay videos from our training classes. Today’s Instant Replay is Edwin Sarmiento talking about how he approaches applying service packs and cumulative updates on Always On Availability Groups: That video is part of the Instant Replay recordings of Edwin’s extensive live 3-day Senior DBA’s Guide to Always On Availability Groups.…
Read More

An Expensive Reason To Avoid AGs In Azure

Cash Rules Most people, when they get through paying for Azure, and SQL Server Enterprise Licensing, are left with a hole in their wallet that could only be filled with something that says “Bugatti”, and has a speedometer with an infinity sign at the end. Recently, while working with a client, I found out that…
Read More

New Class: Always On Availability Groups: The Senior DBA’s Field Guide

Availability Groups are all the rage right now, especially since they’re included with SQL Server 2016 Standard Edition. Our Availability Groups blog post category is one of the most popular on the site, and in my 4-day Senior DBA class, people have always been asking for more in-depth coverage of clustering and AGs. Let’s get together for a…
Read More

New White Paper: How to Build an Always On Availability Group in Google Compute Engine

You’re a database administrator, Windows admin, or developer. You want to build a Microsoft SQL Server environment that’s highly available, and you’ve chosen to use Always On Availability Groups. Our newest white paper – download In this white paper we built with Google, we’ll show you: How to build your first Availability Group in Google…
Read More

Always On Availability Groups Now Supported in Google Compute Engine

I’m excited to finally be able to talk about something Erik, Tara, and I have been working on for the last few months. Here in the SQL Server community, when I mention cloud, you probably think of two companies: Microsoft and Amazon. We’ve been blogging about SQL in AWS for years, and Microsoft throws a…
Read More

When Always On Isn’t: Handling Outages in Your Application

Today’s brief Stack Overflow outage reminded me of something I’ve always wanted to blog about: Stack Overflow is in limp-home mode There’s a gray bar across the top that says, “This site is currently in read-only mode; we’ll return with full functionality soon.” That’s not a hidden feature of Always On Availability Groups. Rather, it’s a…
Read More

Availability Groups: More Planned Downtime for Less Unplanned Downtime

I often hear companies say, “We can never ever go down, so we’d like to implement Always On Availability Groups.” Let’s say on January 1, 2016, you rolled out a new Availability Group on SQL Server 2014. It’s the most current version available at the time, and you deploy Service Pack 1, Cumulative Update 4 (released…
Read More
Tara Kizer

Asynchronous Database Mirroring vs. Asynchronous Availability Groups

When Database Mirroring came out in SQL Server 2005 Service Pack 1, we quickly dropped Log Shipping as our Disaster Recovery solution. Log Shipping is a good feature, but I can failover with Asynchronous Database Mirroring faster than I can with Log Shipping. When Always On Availability Groups (AG) came out in SQL Server 2012,…
Read More

Updated High Availability and Disaster Recovery Planning Worksheet

One of the most popular things in our First Responder Kit is our HA/DR planning worksheet. Here’s page one: Page 1 – how our servers are doing now, versus what the business wants In the past, we had three columns on this worksheet – HA, DR, and Oops Deletes. In this new version, we changed “Oops”…
Read More
Menu