Assume you have configured a transactional replication publisher, which is part of an availability group (AG). Now, you have an asynchronous secondary AG (or mirroring) replica that is offline. Perhaps this is a DR node, and you are doing patching or other planned maintenance on … [Read More]
As a DBA or SQL Developer, you’ve surely encountered a scenario where something worked for you, but not for another user. DBAs usually are part of the sysadmin role, or have a collection of powerful permissions. If I run code as myself, I will never … [Read More]
Starting with SQL Server 2017 CU6 and SQL Server 2016 SP2-CU3, you can now configure your distribution database as part of an Availability Group (AG). I found one spot where a minor change made a few of my scripts blow up.
I’ve used replication and Availability Groups together before. Replication works great with an AG as both a publisher or a subscriber (though, not as a distributor–you can’t add the distribution database to an AG). I was surprised when I recently ran into a problem configuring … [Read More]
Have you ever wondered what the best option is for making your data available in your environment? I was asked by Carlos L Chacon (blog|twitter) to be part of a panel on his podcast for an episode discussing some of the options–availability groups, mirroring, log shipping, and replication. We … [Read More]
FILESTREAM is not a particularly popular feature of SQL Server–if you’re using it, you are in the minority. If you have a database with filestream in an Availability Group, then you’re REALLY in the minority. At my 9-5, this is being done, and it’s apparent that … [Read More]
Availability Groups (AGs) are all the rage these days. Every SQL Saturday, every local Users Group, bloggers and DBAs everywhere are all talking about how cool they are. There’s a lot of talk about how AGs provide a compelling alternative to Failover Cluster Instances (FCIs). … [Read More]