Tracking credit spend and account activity so costs don't surprise anyone
Snowflake provides built-in tools to monitor usage and control costs, primarily through Resource Monitors, the Account Usage and Organization Usage schemas, and various system views/functions that expose credit and storage consumption. Account Admins can set spending limits, receive alerts, and analyze historical usage to optimize warehouse sizing and query efficiency.
1 · Learn the must-know
- Resource Monitors track warehouse credit usage and can trigger actions (NOTIFY, SUSPEND, or
SUSPEND_IMMEDIATE) when defined thresholds are reached, but they only monitor virtual warehouse credits, not storage or cloud services costs. - Resource Monitors can be set at the account level or assigned to specific warehouses, and only users with the ACCOUNTADMIN role can create or modify them.
- The
ACCOUNT_USAGEschema (in the SNOWFLAKE database) provides views likeWAREHOUSE_METERING_HISTORY,QUERY_HISTORY, andSTORAGE_USAGEfor historical monitoring, with data retention up to 365 days but a latency of up to 2 hours (unlikeINFORMATION_SCHEMA, which is near real-time but only retains 7 days-6 months depending on the view). - The
ORGANIZATION_USAGEschema allows monitoring and cost analysis across multiple accounts within an organization, useful for consolidated billing insight. - Auto-suspend and auto-resume settings on virtual warehouses are key cost-control features, automatically pausing idle compute to avoid unnecessary credit consumption.
- The Snowsight web interface includes native cost management dashboards (Account > Usage) that visualize credit consumption by warehouse, query, and time period, helping identify cost drivers without writing SQL.
2 · Check your understanding
A Practitioner needs to audit query text and execution time for warehouse activity from 45 days ago to investigate a cost spike. Querying the table function information_schema.query_history() returns no rows for that period because that function only exposes the trailing 7 days of activity. The Practitioner must retrieve the older query details without exporting any logs manually. Which object should the Practitioner query instead?
What you have tried across SnowPro Core's objectives, not a readiness score.
Snowflake AI Data Cloud Features and Architecture31% of the exam0 of 6 tried
Account Management and Data Governance20% of the exam0 of 3 tried
Data Loading, Unloading, and Connectivity18% of the exam0 of 3 tried
Performance Optimization, Querying, and Transformation21% of the exam0 of 4 tried
3 · Keep going
Ready for more? Take a weighted mock or try free practice questions.