Version Controlled SQL Database Dolt Releases 2.0 with Automatic Storage Cleanup and Compression
By Dillip Chowdary • Jul 20, 2026 • Source: InfoQ
**DoltHub** has released **Dolt 2.0**, a major update to the open source version-controlled SQL database, as reported by Renato Losio for InfoQ. The release introduces integrated storage management capabilities alongside expanded data type handling for versioned relational database workloads.
Technically, **Dolt 2.0** introduces automatic storage optimization, incorporating automated **garbage collection** and **compression**. The release also includes improved engine support for **large data types** and **vector data types**, targeting storage efficiency and data handling across versioned database tables.
For software engineers and database builders, automated **garbage collection** and **storage compression** eliminate manual maintenance routines previously needed to manage storage overhead. Native handling for **large data types** and **vector data types** allows teams to store and query specialized datasets inside a version-controlled SQL database environment.
Within the database market, merging relational SQL query features with Git-like version control creates cumulative disk space demands over time. By integrating automated **garbage collection** and **compression** directly into the engine, **DoltHub** addresses historical storage growth challenges associated with versioned SQL architectures.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Engineering teams considering **Dolt 2.0** should test the new **garbage collection** and **compression** features against their existing table schemas and dataset sizes. Operational metrics on disk usage and query behavior with **vector data types** and **large data types** will provide clear indicators of performance improvements after upgrading.
***
### Summary of Work
Written 5 analytical paragraphs for the Dolt 2.0 release, adhering strictly to the provided source facts without inventing version numbers, dates, metrics, or external details. The text follows the requested five-part structure (what happened, technical detail, impact for engineers, market context, and practical takeaways) with bolded key terms and blank-line paragraph separation.
Advertisement
🔎 More interesting news
- LVSum: A Benchmark for Timestamp-Aware Long Video Summarization
- Cloudflare WAF protects WordPress applications from two high-severity vulnerabilities
- Nuclear startup Valar Atomics in talks to raise new funding at $6B valuation
- OpenAI tweaks chat access in the ChatGPT app for Mac
- Today's full Tech Pulse briefing →