Dolt 2.0 Brings Automatic Cleanup and Storage Compression to Version-Controlled SQL

DoltHub has announced Dolt 2.0, a major release of its MySQL-compatible database that bundles Git-like version control directly into a relational data engine. The update focuses on storage efficiency and performance, adding automated housekeeping features that address one of the platform's historical pain points.

What's New in 2.0#

Dolt 2.0 introduces several features aimed at making the database more practical for production workloads:

• Automatic garbage collection and compression — enabled by default, these features clean up intermediate transaction states that accumulate during operations like bulk imports
• New archive storage format — reduces disk footprint by 30–50% through dictionary-based compression
• Vector index support — beta-stage version control for vector data types, using MariaDB's Vector type
• Performance improvements — Dolt now claims speed advantages over MySQL: 13% faster on writes, 5% faster on reads in sysbench testing

The Storage Challenge#

Dolt uses a copy-on-write architecture where all intermediate transaction states are preserved to disk. This design preserves the full commit history needed for version control, but can accumulate substantial amounts of "garbage"—committed state that never makes it into a named Dolt commit. During large import operations, this intermediate data can consume disk space rapidly. The new garbage collection process automatically identifies and reclaims this orphaned data.

Positioning Against Alternatives#

While Dolt leads as a MySQL-compatible version-controlled database, the broader space includes other Git-inspired tools for data. LakeFS targets data lakes with its own versioning layer, while Nessie offers transactional versioning for lakehouse catalogs. DoltHub also maintains DoltgreSQL, a Postgres-compatible sibling (currently in beta) that shares the same storage engine and version control primitives.

Why Version Control for Data Matters#

As the industry explores Git workflows for data management, the appeal centers on reproducibility and safety. According to analyst commentary on data versioning trends, such capabilities enable "better change management, testing on production data, fast rollbacks, isolated experiments, and most importantly, peace of mind when deploying changes."