Query scope
The Query Scope setting controls whether metrics collect data from a specific time range (Incremental) or from all rows of data (Full Table). Query Scope affects which other Data Collection settings are available, so you typically set it first.
Full Table query scope was designed to support dimension tables (those with no time-based fields), while Incremental query scope is designed to support tables where you want to progressively query consecutive time periods.
- All deep metrics other than SQL metrics inherit the same Query scope as their source table.
- Full Table metric queries may be compute-intensive/expensive on large tables.
- Charts of Full Table metrics are left-aligned: because there are no timestamps, no matter when data collection actually happens, it appears on the chart as occurring at the time it was scheduled to run (based on the polling interval and the polling delay).
The table below gives a summary of the difference between Incremental and Full Table query scope.
| Query Scope | What's collected | Dependent settings | Recommended use case |
|---|---|---|---|
| Incremental | By default, only those rows with a timestamp inside the most recent aggregation interval are collected. If Data Collection Schedule is set to Custom schedule or Triggered, rows from all previous aggregation intervals that haven't already been queried by the metric are collected. | Agg. Interval, Agg. Time Zone, Eval. Delay, Timestamp, Time Zone | Fact tables (tables with a timestamp column) |
| Full Table | All rows, every time the metric query runs. | Polling Interval, Polling Time Zone, Polling Delay | Dimension tables (tables with no timestamp column |
Updated 7 days ago