SQL Server 2019 CU27 is a cumulative update released by Microsoft that delivers targeted fixes for Availability Groups and Change Tracking, along with broader stability and security improvements. If you're running SQL Server 2019 in production, this update is worth your attention regardless of whether you're actively using those specific features.

Cumulative updates aren't glamorous. No one's writing blog posts about how excited they are to apply patches on a Saturday morning. But staying current with SQL Server 2019 CU27 and its predecessors is one of the most straightforward things you can do to keep your environment stable, secure, and supported.

What Is SQL Server 2019 CU27?

CU27 is the 27th cumulative update for SQL Server 2019, released by Microsoft as part of their ongoing servicing model. Microsoft typically releases cumulative updates every 8 weeks during the first year after a product release, then quarterly. Each cumulative update is cumulative in the truest sense: it includes all fixes from every previous CU, so you don't need to apply them in sequence. Installing CU27 gets you everything from CU1 through CU26 as well.

You can download CU27 and review the full fix list on the official Microsoft documentation page.

What Does SQL Server 2019 CU27 Fix?

The two primary focus areas in CU27 are Availability Groups and Change Tracking. Here's what that means in practice.

Availability Groups

Availability Groups are the backbone of high-availability architectures for SQL Server. They're complex, stateful, and sensitive to timing issues, network conditions, and internal synchronisation state. Microsoft's fixes in this area typically address edge cases that surface under specific workload patterns or failover conditions.

If you're running Always On Availability Groups in production, you should treat AG-related fixes as high priority. Bugs in this area can manifest as unexpected failovers, replica synchronisation delays, or in rare cases, data access interruptions. Even if you haven't experienced a specific symptom, applying the fix before you do is the right call.

Change Tracking

Change Tracking is a SQL Server feature that lets applications track which rows have been inserted, updated, or deleted in a table. It's commonly used in data synchronisation scenarios, ETL pipelines, and occasionally in application-level auditing.

The important point Microsoft makes with CU27's Change Tracking fixes is that they can affect you even if you're not actively using Change Tracking. This happens because Change Tracking infrastructure is woven into SQL Server's internal mechanisms. Fixes in this area sometimes address how SQL Server manages internal cleanup tasks, memory structures, or transaction log interactions. Ignoring a fix because "we don't use that feature" is a common mistake that experienced DBAs learn to stop making.

Why Cumulative Updates Matter Beyond the Fix List

Most DBAs know they should apply cumulative updates. Fewer organisations actually do it consistently. The gap between knowing and doing is usually explained by change management friction, testing overhead, or the perception that "if it ain't broke, don't fix it."

Here's the operational reality: SQL Server bugs don't always announce themselves. Performance degradation can be gradual. Memory pressure from a known bug might not trigger an alert until you're already in an incident. Security vulnerabilities don't wait for a convenient maintenance window.

Cumulative updates also matter for supportability. If you raise a support case with Microsoft and you're running an outdated build, the first thing they'll ask is whether you can reproduce the issue on a current CU. Being significantly behind on patching limits your options when something goes wrong.

The general guidance from Microsoft is to apply the latest cumulative update. For production environments, a reasonable practice is to let a new CU sit for 2 to 4 weeks after release, monitor the community for any reported regressions, then schedule your deployment. This balances currency with caution.

How to Apply SQL Server 2019 CU27

Applying a cumulative update to SQL Server 2019 follows a consistent process. Here's a practical overview:

  1. Download the update. Get CU27 from the Microsoft Update Catalog or the SQL Server 2019 CU27 documentation page. Verify the file hash before proceeding.

  2. Review the fix list. Read through the KB articles listed in the CU. Identify any fixes that are directly relevant to your environment and note any that require trace flags or post-installation steps.

  3. Test in a non-production environment first. Run your critical workloads against a restored copy of your production database on the patched instance. This is non-negotiable for business-critical systems.

  4. Back up everything. Take full backups of all databases, including system databases (master, msdb, model). Back up your SQL Server Agent jobs and linked server configurations if they're not already scripted.

  5. Schedule a maintenance window. SQL Server service restarts are required. For Availability Groups, plan a rolling upgrade: patch secondary replicas first, fail over, then patch the former primary. This minimises downtime.

  6. Apply the update. Run the installer as a local administrator. The process is straightforward but can take 10 to 30 minutes depending on the number of databases and system resources.

  7. Verify the build number. After installation, confirm the version with:

SELECT @@VERSION;

SQL Server 2019 CU27 should report build number 15.0.4405.4. Cross-reference this against the SQL Server builds reference if you want a quick lookup.

  1. Monitor post-patching. Watch error logs, performance metrics, and application behaviour for at least 24 to 48 hours after patching. Pay particular attention to any Availability Group replica states and Change Tracking cleanup jobs if you use them.

Should You Skip Versions?

A common question is whether it's safe to jump from, say, CU20 to CU27 without applying the intermediate updates. The answer is yes. Cumulative updates are fully cumulative, so CU27 contains everything in CU21 through CU26. You don't need to apply them sequentially.

What you do need to do is review the fix list for all CUs you're skipping. Some fixes require configuration changes, trace flags, or manual steps that aren't applied automatically by the installer. Skipping the reading is where organisations get into trouble, not the version jump itself.

Key Takeaways

  • SQL Server 2019 CU27 delivers targeted fixes for Availability Groups and Change Tracking, plus cumulative improvements from all previous updates.
  • Change Tracking fixes can affect your instance even if you're not actively using the feature. Don't dismiss fixes based on feature usage alone.
  • Cumulative updates are fully inclusive. You can apply CU27 directly without installing intermediate CUs.
  • A practical patching approach is to wait 2 to 4 weeks after release, test in a non-production environment, then deploy during a scheduled maintenance window.
  • Staying current with cumulative updates is a baseline requirement for Microsoft support and a core part of any responsible SQL Server maintenance programme.

Need Help Staying Current?

Keeping SQL Server environments patched and healthy is straightforward in principle and genuinely time-consuming in practice. Testing updates, managing maintenance windows across multiple instances, and monitoring for regressions all take dedicated effort.

DBA Services provides managed SQL Server support and regular health checks for Australian organisations running SQL Server 2019 and other versions. If your patching is behind, or you're not confident your update process is as solid as it should be, we can help you get on top of it and keep it that way. Get in touch to find out what a proactive SQL Server maintenance programme looks like for your environment.