• Man at desk looking concerned at computer screen showing automatic synchronization failure error

    SQL Server AG Auto Seeding Fails With “Has Not Been Rolled Forward to a Point in Time” And How To Fix It

    I ran into an interesting issue a while back while trying to seed a database in an Availability Group via automatic seeding. I wanted to share the experience, found error, and resolution. Hopefully this can help someone who is facing a similar issue. Now, before we get started, for large databases across slow or multi-subnet…


  • Robotic arms working on electronic circuit boards in a factory

    DBAOps Pt.3: Automating A Full SQL Server AG Lab With Hyper-V And PowerShell From Zero To Synchronizing

    Before we begin, I first and foremost would like to give credit to Amy Abel for this idea. I’ve been blogging over the past few weeks about how the DBA role is evolving and there is a shift in mindset to have when approaching projects and tasks. I have mentioned before that I was a…


  • Security officer in uniform focused on unlocking a door with a key.

    Configuring gMSA Accounts for SQL Server and Availability Groups: The Complete Gotcha List

    So, you’re making a valiant effort to improve your security posture in your SQL Server estate and have decided to move to Group Managed Service Accounts (gMSAs). But, after switching from your local account running SQL, or your domain account, you’re staring at Configuration Manager telling you that “It could not start the service in…


  • Mechanical robotic mule carrying multiple servers and data storage units on a mountain path

    Contained AG Not Synchronizing After Planned Failover: How ADR Saved Us

    We had a SQL Server 2022 contained AG that consistently took exactly 10 minutes to recover after every planned manual failover. Not 9 minutes. Not 11. 10 minutes on the dot. Both replicas would sit in a Not Synchronizing state, every database showed Recovering, and our fastest path back to being online again was often…


  • Humanoid robot holding a tablet showing system analysis, interacting with smiling IT specialist in office.

    We Built an AI-Assisted Operating Model for SQL Server Migrations

    Disclaimer/ Edit: This post was heavily “polished” and rewritten with AI. The content is mine and true but I’m sure you’ll detect the AI patterns in this one :). The Problem with Traditional DBA Operations If you’ve worked in enterprise SQL Server long enough, you know how migrations usually go. A request comes in to…


  • Database Crash Recovery Takes Forever After Planned Manual Failover

    Weekend Patching, Business As Usual Today I was patching a bunch of servers at a client as Microsoft released their most recent Security Patch for SQL Server that addresses an exploit / vulnerability found after patch Tuesday. Read more on it here. I went through the normal patching routine for an AG; working through all…


  • Read-Only Routing Isn’t Working, What Gives?

    Problem You want to implement read-only routing for your Always on Availability Group so your reading workloads can be offloaded from your primary replica to one of your secondary replicas. But when it comes time to test, your reading queries aren’t hitting your readable secondary replicas like you expected. What gives? Here are some things…


  • ChatGPT Series Part 3: Understanding SQL Server High Availability and Disaster Recovery Options

    Part 3 in the ChatGPT series where ChatGPT gives me topics to blog about; High Availability and Disaster Recovery (HADR) options. There are several options SQL Server offers to keep your databases both highly available, and redundant in the event of a disaster. The three I’d like to chat about today are: Always on Availability…


  • How to Set up Replication in an Always On Availability Group

    Replication can be a daunting technology to work with at times. Combine that with Always on Availability Groups (AAGs) and you may find yourself in a head scratcher of a situation. When deploying replication on a standalone server, it is not uncommon to see that same server act as a local distributor, meaning the distribution…