Skip to main content

sqb audit

Runs all attached audits without rebuilding models. Useful for verifying data quality on existing warehouse state.

Usage

Flags

Concurrency

Standalone audits run serially by default. Use --concurrency to opt into parallel warehouse queries:
SQLBuild resolves the limit in this order: an explicit --concurrency value, the SQLBUILD_CONCURRENCY environment variable, the effective project settings.concurrency, then the product default of 1. Values must be at least 1. The physical worker count is bounded by the number of selected audits. Each active worker opens and exclusively uses one warehouse connection, so higher concurrency can increase warehouse load and cost. Results and final JSON remain in plan order even when queries finish in a different order. If an audit query raises a runtime, adapter, or framework error, SQLBuild records that failure and continues running the remaining independent audits. After all selected audits have been attempted, it reports every query failure in plan order and exits nonzero. Failed queries do not produce fabricated audit results. Interruption and cancellation are different: SQLBuild stops scheduling new audits, drains queries that have already started, and then closes every worker connection. Generic adapters cannot guarantee immediate cancellation of a query already running in the warehouse.

Examples