Spanner DML Statements Now Enforce 80K Mutation Limit Per Statement
Google Cloud Spanner now enforces its 80,000 mutation limit for DML statements on a per-statement basis, rather than cumulatively across an entire transaction. This enhancement provides greater flexibility, enabling transactions to include multiple DML statements that might collectively surpass the old cumulative limit, provided each individual statement adheres to the 80,000 mutation cap. The change primarily affects developers and database administrators executing complex DML operations in Spanner. For the Mutation API, the 80,000 limit still applies to all mutations within a commit, and all transactions remain subject to a 100 MiB commit size limit.
Features (1) ›
- Spanner
For DML statements, Spanner now enforces the 80,000 mutation limit (including indexes) per statement rather than cumulatively across the transaction. This allows a transaction to execute multiple DML statements that collectively exceed the limit, as long as each individual statement remains under it. For the Mutation API, the 80,000 limit applies to all mutations in the commit. All transactions are still subject to the 100 MiB commit size limit.
https://docs.cloud.google.com/release-notes#August_11_2026
Related releases
- Assured Workloads enhances data residency controls and ITAR support Google Cloud release notes ·
- Google Cloud details Hive Metastore modernization with Lakehouse runtime catalog Google Cloud Blog ·
- Cloud SDK 580.0.0 Updates Include Deprecation, New Features, and GA Promotions Google Cloud release notes ·
- Looker's Semantic Layer Integrates with Gemini Enterprise for Governed AI Analytics Google Cloud Blog ·
- Spanner: Dynamic Channel Pooling now GA for Go and Java Clients Google Cloud release notes ·
- Target Showcases Enhanced Retail Discovery and Reduced Database Maintenance with Spanner Graph Google Cloud Blog ·