Launch week: the Season Pass & Fundamentals Week are 50% off — ends in 15d 19h 18mSee the sale

Category: High Availability

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 about Adding Managed Instances to SQL Server Distributed Availability Groups Be the first to comment
News & Opinion

Training Week: Announcing Edwin’s New Class on Failover Clustered Instances

This week, we've got a bunch of announcements about new training classes. Next up, Edwin Sarmiento: his 3-day Always On Availability Group class has been getting great reviews:
"This class is fantastic. There is no filler, and no needless repetition, so be prepared to pay attention the entire duration. Edwin clearly is very passionate about his craft and does an incredible job of sharing his knowledge. Great balance of theory and application. I went through 4 glitter pens taking notes. A+" - Jordan

Read more about Training Week: Announcing Edwin’s New Class on Failover Clustered Instances 2 comments — Join the discussion

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 live 3-day online class to cover:

Read more about New Class: Always On Availability Groups: The Senior DBA’s Field Guide Be the first to comment

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.

In this white paper we built with Google, we’ll show you:

Read more about New White Paper: How to Build an Always On Availability Group in Google Compute Engine 21 comments — Join the discussion
Production DBA

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 ton of marketing money at the SQL Server community, talking about Azure at every possible conference and user group.

Read more about Always On Availability Groups Now Supported in Google Compute Engine 6 comments — Join the discussion
News & Opinion

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 2015/12/22). You're fully current, and it's a stable engine from 2014 - how many more bugs can they find, right?

Read more about Availability Groups: More Planned Downtime for Less Unplanned Downtime 10 comments — Join the discussion
Production DBA

The Cost of Adding a Reporting Server

"We'd like to offload our reporting queries to a separate SQL Server."
The first costs are fairly obvious.
Hardware and storage - even if you're running it in a virtual machine, you need to account for the costs of say, 4 cores and 32GB RAM. Not only will you need storage for the databases, but you'll also need to decide whether this server gets backed up, and copied to a disaster recovery data center.

Read more about The Cost of Adding a Reporting Server 9 comments — Join the discussion

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, we were excited to get rid of Transactional Replication, Failover Clustering and Database Mirroring. It solved our reporting needs (your mileage may vary), our High Availability needs and our Disaster Recovery needs.

Read more about Asynchronous Database Mirroring vs. Asynchronous Availability Groups 19 comments — Join the discussion