Skip to main content
Query limits help control resource usage by restricting the time and size of query execution. They prevent excessive memory consumption and long‑running queries that can impact overall system performance.

​
Why use query limits

  • Avoid resource overloads: Large queries can consume significant memory and CPU.
  • Improve stability: Prevents the system from being blocked by expensive queries.
  • Ensure fairness: Keeps dashboards responsive for all users.

​
What query limits can be set

You can define limits for:
  • Processing time: Maximum time allowed for a query to run.
  • Result size:
    • Intermediate limit: Maximum number of results per retrieval step.
    • Transient limit: Maximum cumulative results across all steps.
  • Concurrent Mdx queries: Maximum number of Mdx queries that are process at the same time.

​
When to use query limits

Query limits are most effective when:
  • Dashboards contain complex widgets that require a high number of queries.
  • Users run queries with large cross‑joins.
  • You need to prevent accidental resource overloads.
  • You need to restrict the resource usage of group of users.
Avoid setting limits too low, as this may cause valid queries to fail.