Symptoms:
- Unexpected overage warnings in SQL query usage, despite running queries on a small dataset.
- Concern about exceeding SQL query limits during beta testing (or any testing below 50,000 MAU).
- Confusion regarding how SQL query limits are applied and whether charges will be incurred.
Cause:
The SQL query usage limits displayed in the Analytics dashboard reflect the Fair Usage Limits applied to all Unity Analytics projects. These limits are only relevant if the project exceeds the Free Tier threshold of 50,000 Monthly Active Users (MAU). Users within the Free Tier may see overage percentages but are not subject to charges.
Resolution:
- The Fair Usage Limits are only enforced for billing purposes if a project exceeds 50,000 MAU.
- If the project in question is expecting less than 50,000 players, there is no risk of exceeding the Free Tier and incurring charges.
- If a project exceeds 50,000 MAU, it will receive a minimum of ~42 minutes of SQL querying time, significantly more than the small-scale queries being executed with a project with a low MAU.
- Users can continue experimenting with SQL Data Explorer without concern unless their MAU grows beyond the Free Tier threshold.
More Information:
For additional details on Unity Analytics Fair Usage Limits and Free Tier thresholds, refer to the official Unity documentation: Unity Analytics Fair Usage Limits.
If you have further questions, feel free to reach out to Unity Support.