live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
nl2sql.ai
newsCOST CONTROL

Snowflake’s per-user AI quotas turn cost controls into access controls

The 10.29 release lets administrators cap individual AI-credit use and automatically block new requests across Cortex Agents, Snowflake CoWork, CoCo and AI Functions.

By The News Desk· Aug 19, 2026the quick take — two AI hosts go live when you do

Snowflake has made per-user quotas generally available, moving AI cost governance from account-wide monitoring toward individual enforcement. In the 10.29 release, administrators can set daily and monthly credit limits for each user and apply them to AI Functions, Cortex Agents, Snowflake CoWork and Snowflake CoCo, as well as track warehouse compute in a separate quota. For supported AI domains, Snowflake can automatically block access when a user reaches the limit and release the block when the quota cycle resets. Snowflake’s 10.29 release notes describe the GA rollout and its changes from preview.

What administrators can control

A quota can cover every user in an account or a subset selected through user tags, allowing teams or cost centers to share one policy while each user’s usage is evaluated independently. The same per-user limit applies to everyone inside a given quota; Snowflake does not support different limits for different users in that object or a pooled cap across the group. Daily cycles reset at UTC midnight, and monthly cycles follow the UTC calendar month. The quota documentation also says administrators can configure actual-spend or projected-spend thresholds for notifications and custom actions.

At GA, Snowflake added separate monthly or daily notification-threshold targeting and made end-user emails for blocks configurable. It also introduced an account-level QUOTA_ACCESS_BLOCK_HISTORY view and replaced the preview GET_ACTIVE_BLOCKS() method with GET_ACTIVE_BLOCKS_V2(). The preview-only usage and refresh-tier methods were removed because Snowflake now says quota evaluation runs within minutes for all accounts. Those API changes are listed in the release notes.

The operational catch

The controls are not request-time hard ceilings. Snowflake says enforcement is evaluated within minutes after spend is recorded, so a user can overshoot before a block lands; a single large AI-function request can overshoot by more than interactive use. Configuration changes can take roughly five to ten minutes to propagate. Blocking applies only to supported AI domains: warehouse credits can be monitored, but warehouse queries are not stopped by the built-in block action. Snowflake documents those limitations explicitly.

For teams rolling out data agents broadly, that distinction matters. The feature provides a native kill switch for runaway individual AI consumption, but administrators still need conservative limits, notification thresholds and monitoring rather than treating the quota as an instantaneous billing boundary.

sources

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk