Schema:

ACCOUNT_USAGE

DATA_QUALITY_MONITORING_USAGE_HISTORY view

The DATA_QUALITY_MONITORING_USAGE_HISTORY view in the ACCOUNT_USAGE schema records the daily credit consumption for data metric function evaluations on tables in an account within the last 365 days (1 year).

See also:

Introduction to data quality checks

Columns

Column NameData TypeDescription
START_TIMETIMESTAMP_LTZStart of the specified time range.
END_TIMETIMESTAMP_LTZEnd of the specified time range.
CREDITS_USEDNUMBERNumber of credits billed for data metric function evaluations on the table.
TABLE_IDNUMBERInternal/system-generated identifier for the table monitored by data metric functions.
TABLE_NAMEVARCHARName of the table.
SCHEMA_IDNUMBERInternal/system-generated identifier for the schema that stores the table.
SCHEMA_NAMEVARCHARName of the schema that stores the table.
DATABASE_IDNUMBERInternal/system-generated identifier for the database that stores the table.
DATABASE_NAMEVARCHARName of the database that stores the table.

Usage notes

Latency for the view may be up to 180 minutes (3 hours).

Snowflake can evaluate anomaly detection checks for multiple tables in a schema as a batch. This view attributes the batch’s compute cost to the participating tables in proportion to the number of data metric function (DMF) associations for each table in the batch. For example, if a batch contains two DMF associations for one table and one for another, approximately two-thirds of the batch’s compute cost is attributed to the first table and one-third to the second. These proportions describe cost allocation within a batch. They don’t imply that the batch costs the same as evaluating each DMF separately.

This allocation applies to schema-level anomaly detection. It doesn’t change how costs are attributed for individual table evaluations.