Define the boundary
Timestamps, counts, job stats — not order lines.
Learn · Security
Metadata-only monitoring
Why rows should never leave the warehouse for reliability.
The problem
Row sampling sounds insightful until security review stalls the deal for six weeks.
The outcome
Monitor with INFORMATION_SCHEMA, job stats, and dbt artifacts — never result rows.
Reads
Metadata + artifacts
Rows
Stay in BQ
Review
Faster
What you get
Least-privilege SA
Document roles; revoke anytime.
Artifacts ≠ exports
run_results.json is not SELECT *.
Write it publicly
/security should survive a skeptical reviewer.
- ✓Security: /security
- ✓Blog: /blog/metadata-only-is-a-feature
- ✓Trust: /trust
- ✓Start: /start
Try VectorData, then decide
Open workspace, or book a Data Stack Health Audit credited toward Managed.