Availability Groups: 5 Things

Here are some configurations that I feel are worth noting about AlwaysOn Availability Groups.  There are plenty of other best practices and configuration guides around but these are issues I’ve experienced when supporting existing AlwaysOn AGs and have therefore re-configured them or added these configurations to my standard AG builds. Continue Reading

Automating SQL Service Packs and Cumulative Updates

Applying Service Packs and Cumulative updates is dull, mundane work. It’s hard to keep on top of sometimes and also with some 24/7 databases, it’s hard to find an update window. Sometime it’s hard to even get the business to agree to something if they’re not exactly seeing any end Continue Reading

Index Maintenance and Availability Groups

I have a very large database which I migrated to a virtual server and then implemented AlwaysON availability groups. It’s a 3 node cluster with one Primary (obviously), a Synchronous read-only secondary and an asynchronous non-readable node in a DR data centre. One thing that was very noticeable after the Continue Reading

SQL Agent and AlwaysON Availability Groups

So we all know that SQL Agent isn’t part of an availability group and therefore (like logins, operators, alerts, linked servers etc) your SQL jobs won’t sync. But even when they are synced, I’m sure there are plenty that should only run on the Primary Node and therefore shouldn’t run Continue Reading

But I’m only running Select Queries!

Just because you only have db_datareader access to production doesn’t mean you can’t cause a great deal of harm. I’ve worked in a few areas where against my advice, we have developers, analysts and report writers who  still have access to Production Environments. Normally most business owners have finally relented Continue Reading

Restoring Secondary Nodes in an AlwaysON Availability Group

There have been a few scenarios where I have had to create a fresh backup of a database and restore the secondary nodes in an Availability Group. Normally the route cause has been when a secondary node has stopped syncing due to hardware failure, excessive log growth, low bandwidth or Continue Reading