BigQuery: Exceeded rate limits — too many concurrent DML statements / table update operations
Too many UPDATE/DELETE/MERGE statements (or table metadata updates) hit the same table at once.
Exceeded rate limits: too many table update operations for this tableExceeded rate limits: too many concurrent DML statementsBigQuery rateLimitExceeded DMLJob exceeded rate limits: Your table exceeded quota for imports or query appends per tableexceeded quota for table update operations Meaning
BigQuery queues DML per table (up to 20 concurrent, with limits per day). Batch changes into fewer larger statements, use MERGE, load via temporary tables, prefer append-only designs with streaming/partition replace, and retry with backoff for rateLimitExceeded.
Common causes
- Many small DML statements
- Concurrent writers to one table
- Row-by-row updates
- Table metadata updates too frequent
- Quota for table operations
⚡ Quick fix
- Batch into a single MERGE/INSERT SELECT
- Serialise writers or use a queue
- Retry with exponential backoff
Detailed fix by platform
SQL
MERGEproj.ds.targetT USINGproj.ds.stagingS ON T.id = S.id WHEN MATCHED THEN UPDATE SET v = S.v WHEN NOT MATCHED THEN INSERT (id, v) VALUES (S.id, S.v);
How to diagnose
- DML — Many small?
- Writers — Concurrent?
- Backoff — Used?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 429 Cloud Storage 429: rate of change requests to a single object exceeded (1 write per second)
- 429 RESOURCE_EXHAUSTED: Quota exceeded for quota metric Google API: 429 RESOURCE_EXHAUSTED — Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute per user'
- BigQuery: Access Denied: Project: User does not have bigquery.jobs.create permission BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026