SQL Server 2025: Faster Backups with ZSTD Compression!


SQL Server 2025: Faster Backups with ZSTD Compression

Hi Guys!

One of the most practical improvements in SQL Server 2025—and a very welcome one for DBAs constantly fighting backup windows—is the new support for Zstandard (ZSTD) compression. This modern compression algorithm delivers faster backups without significantly increasing CPU or sacrificing storage savings.

What’s New Compared to Previous Versions

Up to SQL Server 2022, backup compression relied on MS_XPRESS, with optional acceleration via Intel QAT (or software fallback using QATzip). But now with SQL Server 2025, Microsoft introduces ZSTD: an open-source, high-speed compression algorithm with flexible levels and excellent performance-to-compression ratios.

How to Use It

No new UI, no new tools. It’s all in T-SQL: 



BACKUP DATABASE YourDB 

TO DISK = 'YourPath\backup.bak'

WITH COMPRESSION (ALGORITHM = ZSTD, LEVEL = LOW|MEDIUM|HIGH);
  • LOW is the default and fastest
  • MEDIUM and HIGH offer stronger compression but take more time

Performance Benchmarks (Real World)

🧪 Pythian (50 GB DB, local disk D:)

  • No Compression: 24 s (1882 MB/s)
  • MS_XPRESS: 4 min 30 s (179 MB/s, CPU 17%)
  • ZSTD LOW: 2 min 10 s (362 MB/s, CPU 15%)
  • ZSTD MEDIUM: 3 min 30 s (226 MB/s)
  • ZSTD HIGH: 18 min 10 s (43 MB/s)

✅ Result: ZSTD LOW cuts backup time in half compared to MS_XPRESS, with similar or better CPU usage and compression.

🧪 Anthony Nocentino (389 GB DB, backup to S3)

  • No Compression: 390 GB → 259 s (1533 MB/s, CPU 35%)
  • MS_XPRESS: 219 GB → 441 s (902 MB/s, CPU 85%)
  • ZSTD LOW: 267 GB → 246 s (1621 MB/s, CPU 80%)
  • ZSTD MEDIUM: 211 GB → 603 s (660 MB/s)
  • ZSTD HIGH: 209 GB → 1112 s (358 MB/s)

✅ Result: ZSTD LOW is faster than uncompressed, with near-MS_XPRESS compression, much lower CPU, and significantly faster backup times.

🧪 Haloui / dbi-services (StackOverflow DB, 8 vCPU VM)

  • MS_XPRESS: ~290 s (563 MB/s)
  • ZSTD LOW: ~171 s (954 MB/s)

✅ Result: ~41% faster than MS_XPRESS, with comparable CPU usage.

What This Means for You

  • ZSTD LOW is your go-to for fast backups: often faster than uncompressed, yet still provides good compression.
  • ZSTD MEDIUM is useful when space matters more than time.
  • ZSTD HIGH gives maximum compression—but it’s slow, and mostly suited for archival scenarios.

Final Thoughts

SQL Server 2025's ZSTD compression offers a serious upgrade for backup performance. If your current full backups are eating up your maintenance windows, try: 



WITH COMPRESSION (ALGORITHM = ZSTD, LEVEL = LOW)

You’ll often see backup durations cut in half, while still benefiting from compression—without hammering your CPU.

As always: benchmark in your environment. Every workload is different, and the best setting is the one that balances your speed, CPU, and storage constraints.

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

La clausola NOLOCK. Approfondiamo e facciamo chiarezza!

Image
Ehi ragazzi! La domanda è di quelle importanti! Siete pronti per scoprire tutto ma proprio tutto sulla clausola NOLOCK?   Se la riposta è si, allora seguitemi! Oggi ne spiegheremo il funzionamento in maniera approfondita. Faremo una introduzione al concetto di tipi di LOCK Ed infine vedremo come mai una SELECT ne può bloccare un'altra. Non vi nascondo che il motivo di questo articolo è fare chiarezza. Su questo argomento si sentono spesso affermazioni “curiose” ma tra le tante questa è la prima: “ uso la SELECT con l’opzione WITH(LOCK) così non blocco le altre tabelle ”.   Ma, è proprio vero quanto affermato? Beh oggi facciamo il punto!   Buona lettura!     La clausola NOLOCK Diciamo subito per iniziare che cos’è la NOLOCK. NOLOCK è il nome di una clausola che è possibile specificare all’interno di uno statement di tipo SELECT utilizzando la seguente sintassi: SELECT * FROM TABELLA WITH (NOLOCK) Si noti che non possiamo ...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more