If you're on a query runs pricing plan, this document helps you understand how it is calculated.

What are query runs?

A query run is when a SQL query gets sent from Holistics to your analytics database to retrieve a data result. For example, a query run occurs when a report is viewed, an email schedule is triggered, or a data import is triggered.

Examples of query runs include cases such as:

  1. For each widget (or report) in a dashboard that's accessed with specific filter parameters. Or when a report is accessed.
  2. When a dataset is explored, or an adhoc SQL query is run.
  3. ELT schedules and scheduled runs that refreshes or updates data

Contact [email protected] if you'd like to find out more details.

Name Note
Chart in Dashboard Each chart when run will count as 1 query run
Dashboard Schedule Delivery (Email, Slack) Each schedule when run will take up query runs based on the number of charts in the dashboard as each report will request fresh data.
Explore dataset Each dataset explore will cost 1 query run
Load data from external source (Import Model) Each run will cost 1 query run
Materialized run to persist SQL transforms into DW (Model Persistence) Each run will cost 1 query run

Can you walk me through an example?

Sure! Say that you have a dashboard with 8 charts (widgets) and a bunch of filters below.

You also toggle on the cache settings for 6 hours, which means the chart results will be cached for 6 hours after each run.