BigQuery Data Transfer Service limits the maximum rate of incoming requests and enforces appropriate quotas on a per-project basis. Specific policies vary depending on resource availability, user profile, service usage history, and other factors, and are subject to change without notice.
The lists below outline the current rate limits and quota limits of the system.
Load jobs created by transfers are included in BigQuery's
quotas on load jobs. It's important to consider
how many transfers you enable in each project to prevent transfers and other
load jobs from producing
You can use the following equation to estimate how many load jobs are required by your transfers:
Number of daily jobs = Number of transfers x Number of tables x
Schedule frequency x Refresh window
Number of transfersis the number of transfer configurations you enable in your project.
Number of tablesis the number of tables created by each specific transfer type. The number of tables varies by transfer type:
- Campaign Manager transfers create approximately 25 tables.
- Google Ads transfers create approximately 60 tables.
- Google Ad Manager transfers create approximately 40 tables.
- Google Play transfers create approximately 25 tables.
- Search Ads 360 transfers create approximately 50 tables.
- YouTube transfers create approximately 50 tables.
Schedule frequencydescribes how often the transfer runs. Transfer run schedules are provided for each transfer type:
Refresh windowis the number of days to include in the data transfer. If you enter 1, there is no daily backfill.
Although scheduled queries in BigQuery use features of the BigQuery Data Transfer Service, they are not transfers and are not subject to the load jobs quota. Scheduled queries are subject to the same BigQuery quotas and limits as manual queries.