If you’re not familiar, T-SQL Tuesday is a blogging party hosted by a different person each month. It’s a creation of Adam Machanic (b|l|t), and it’s been going on for ages now! Basically the host selects a topic, defines the rules (those are almost always the same), and then everyone else blogs about it. Once the deadline is reached, the host summarizes each of the submitted posts on their site/blog.
This month’s topic is, “my favorite SQL Server feature,” and is hosted by Jens Vestergaard.
I’m choosing database mirroring as my favorite SQL Server feature not only because of its raw awesomeness but also because it released with SQL Server 2005 SP1. Today marks the end of SQL Server 2005’s mainstream support and I felt it was fitting to send it off with a celebration of one of its best features.
Database mirroring is so many things.
- High-availability feature.
- Flexible. It works with AD, certificates, in-domain, cross domain, etc.
- Tried and true. With over a decade of life the database mirroring feature is mature and stable.
- Setting the stage. Microsoft is throwing a lot of chips on the Availability Group feature which was inspired and based on database mirroring.
- Available in Standard Edition!!!
- FAST FAILOVERS! In Argenis Fernandez‘s presentation (Near) Zero-Downtime Upgrades he points out that mirroring fails over even faster than Availability Groups.
With the end of SQL Server 2005, we also will soon see the end of database mirroring. There is a new feature releasing with SQL Server 2016 called Basic Availability Groups. This is the replacement for database mirroring. The use cases and limitations will appear very similar to database mirroring but it will use the Availability Group technology. In theory this will be like a stim-pack for the database mirroring feature while leaving it available in Standard Edition. Let’s cross our fingers that the Windows Failover Cluster components don’t slow down the failovers like it did with AGs.