The SQL Layer Did Not Follow the Rename: SNOWFLAKE INTELLIGENCE Is Still the Live DDL Keyword, No Bundle Retires It, and the Only Real Break Is Three Renamed Columns
The question
"Is SNOWFLAKE_INTELLIGENCE_USAGE_HISTORY still queryable as an ACCOUNT_USAGE alias, and does any Snowflake behavior-change bundle schedule retiring the SNOWFLAKE INTELLIGENCE DDL keyword or object name?"
Context: this closes the first open follow-up of [[2026-09-15-snowflake-intelligence-vs-cowork-naming-standard]], which established that the product name is retired in docs and billing but left the SQL layer unresolved. It decides whether phData client runbooks and GRANT scripts that name the old identifier need a migration note.
Headline: Three layers, three different answers. The product name is retired (already established, not re-derived here). The view name is gone from current docs in both ACCOUNT_USAGE and ORGANIZATION_USAGE, with no deprecation notice anywhere, and three of its columns were silently renamed. The DDL keyword, object type and privilege names are still SNOWFLAKE INTELLIGENCE in today's docs, verbatim, across create, alter, show, grant, tagging and budget surfaces. No behavior-change bundle schedules any retirement: all eight 2026 monthly bundles contain zero references to this product, keyword or view. The migration note belongs on cost-monitoring queries only. GRANT scripts naming SNOWFLAKE INTELLIGENCE are currently correct and should not be touched.
What we already know (from the vault)
- The parent brief established that "Snowflake Intelligence" is retired as a product name and is not a documented alias: docs, pricing and billing surfaces say "Snowflake CoWork" only, and the old view doc URL returns HTTP 308. It flagged the SQL layer as unresolved and explicitly warned "don't assume
SNOWFLAKE_INTELLIGENCE_USAGE_HISTORYstill works." [[2026-09-15-snowflake-intelligence-vs-cowork-naming-standard]] - The parent brief also predicted the mechanism now confirmed: "renaming DDL keywords usually needs a behavior-change bundle and a deprecation window, and we found none announced." That prediction holds at a much higher evidence level today. [[2026-09-15-snowflake-intelligence-vs-cowork-naming-standard]]
- The rename was announced 2026-06-02 at Summit; the core agent went GA 2025-11-04 under the old name, so roughly seven months of client-side artifacts carry the old term. [[2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix]]
- The admin step for publishing an agent was already described in the vault as adding it to "the Snowflake Intelligence Object," an early signal that the object name survived the product rename. [[2026-07-08-cortex-agent-cowork-skill-native-publish]]
- The vault has a standing naming trap here: "Cowork" in phData's internal architecture is Anthropic's Claude Cowork, not Snowflake CoWork. [[2026-09-13-cortex-code-client-deployable-surface-p3-p4]]
- Precedent for how to read a pending-bundle answer in this product area: a prior brief tracked a Cortex cross-region behavior change through the bundle system rather than through marketing pages. [[2026-09-13-cortex-code-client-deployable-surface-p3-p4]]
What the web says
All items below verified against docs.snowflake.com on 2026-11-08.
- Layer (ii), the view name:
SNOWFLAKE_COWORK_USAGE_HISTORYis the only documented name, in both schemas. The complete 194-page ACCOUNT_USAGE page index listsSNOWFLAKE_COCO_USAGE_HISTORYandSNOWFLAKE_COWORK_USAGE_HISTORYand nothing under the old name. The ORGANIZATION_USAGE index is identical in that respect. Both old doc URLs return HTTP 308 to the CoWork pages; the Markdown variant of the old ACCOUNT_USAGE URL is a hard 404. (ACCOUNT_USAGE index; ORGANIZATION_USAGE index) - No deprecation notice exists for it, and that absence is meaningful because the same index does mark deprecations. The ACCOUNT_USAGE reference carries explicit rows of the form "This view is deprecated. Use the BACKUP_OPERATION_HISTORY view instead," and labels the retired SNAPSHOT_* views "— Deprecated" in its page list. No such row or label exists for the old view. So: not present in the current ACCOUNT_USAGE or ORGANIZATION_USAGE view reference as of 2026-11-08, and carrying no deprecation notice — which is not the same as being removed from the engine. (ACCOUNT_USAGE view reference)
- Three columns inside the view were renamed, and this is the one genuine break. An Internet Archive capture of Snowflake's own page dated 2026-03-09 documents
SNOWFLAKE_INTELLIGENCE_ID,SNOWFLAKE_INTELLIGENCE_NAMEandSNOWFLAKE_INTELLIGENCE_TAGS. Today's page documentsSNOWFLAKE_COWORK_ID,SNOWFLAKE_COWORK_NAMEandSNOWFLAKE_COWORK_TAGS.USER_NAMEandPARENT_REQUEST_IDwere present in March too, so nothing was added there. ASELECTlist naming the old columns breaks regardless of whether the view name itself still resolves. (current view page; archived 2026-03-09 capture) - Layer (iii), the DDL and privilege surface: still
SNOWFLAKE INTELLIGENCE, everywhere, verbatim. Current CoWork admin docs carryCREATE SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT,ALTER SNOWFLAKE INTELLIGENCE ... ADD AGENT,SHOW SNOWFLAKE INTELLIGENCES, and the privilegesCREATE SNOWFLAKE INTELLIGENCE ON ACCOUNT,USAGE ON SNOWFLAKE INTELLIGENCEandMODIFY ON SNOWFLAKE INTELLIGENCE. The UI-created object is namedSNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULTand the docs state you cannot choose a different name. This is the page a runbook is written from. (User access and settings for agents; Getting started with Snowflake CoWork) - The old name is also load-bearing in budgets, tagging and account parameters. Shared resource budgets take the domain as the string literal
'SNOWFLAKE INTELLIGENCE'inADD_SHARED_RESOURCEandSYSTEM$REFERENCE, and reportSERVICE_TYPEasSNOWFLAKE_INTELLIGENCEandENTITY_TYPEasSNOWFLAKE INTELLIGENCE. Cost-center tagging usesALTER SNOWFLAKE INTELLIGENCE IF EXISTS ... SET TAG. Identity routing usesLOGIN_IDP_REDIRECT = (SNOWFLAKE_INTELLIGENCE = ...)andALLOWED_INTERFACES = (SNOWFLAKE_INTELLIGENCE). Even the new CoWork view documents a taglevelenum value of"SNOWFLAKE_INTELLIGENCE". (Resource budgets for Snowflake CoWork; CoWork shared resource budgets) - This object type has no SQL command reference page at all, under either name. The complete 778-page SQL Commands index lists
CREATE AGENT,ALTER AGENT,SHOW AGENTSand the external-agent equivalents, but zero entries matching intelligence, cowork or coco. The keyword lives only in user-guide code blocks. There is therefore no reference page that a rename would have to update, which partly explains why no rename paperwork exists. (SQL Commands index) - The behavior-change answer is a clean no. All eight 2026 monthly bundles (2026_01 through 2026_08) were retrieved and searched: zero references to this product, view or keyword. The current pending bundle is 2026_08, introduced in the 10.37 release (October 8-16, 2026) as Disabled by Default; 2026_07 moved to Enabled by Default in that same release. The unbundled behavior-change list has four CoWork entries, and all four are behavioral rather than nominal: runs proceeding when tools are inaccessible (September 2, 2026),
EXECUTE AGENT TASKgranted to PUBLIC (July 27-29, 2026), dashboard data access defaulting to TRUE (October 26, 2026), and MANAGE ACCESS on artifacts to PUBLIC (pending). None renames anything. (Behavior change announcements; Unbundled behavior changes) - Snowflake does route SQL-identifier renames through this channel, which makes the silence informative. Documented precedents:
TOKEN_SEARCHrenamed toSEARCH(bundle 2024_05), theCREATE DATA EXCHANGE LISTINGprivilege renamed toCREATE LISTING(bundle 2025_03), and a column rename inSHOW VERSIONS IN MODELoutput (bundle 2024_07). The closest analogue is Notebook Project Objects renamed to Code Bundles, published as an unbundled behavior change whose note reads that existingCREATE/EXECUTE NOTEBOOK PROJECTstatements continue to work and no migration is required. Snowflake's behavior-change policy gives account admins at least eight weeks of testing and opt-out control before any such change is generally enabled. (Behavior change policy; bundle 2025_03 privilege rename) - The view rename itself was published with no release note, unlike its sibling. The release-notes index contains dated notes for the old view's preview (February 18, 2026) and GA (February 25, 2026), both still titled with the old identifier and still linking the redirecting URL, and a dated GA note for
SNOWFLAKE_COCO_USAGE_HISTORY(August 17, 2026). There is no dated release note announcingSNOWFLAKE_COWORK_USAGE_HISTORY. Snowflake also retroactively rewrote historical release-note titles to the new product name while leaving the old URL slugs intact, which is why "Nov 04, 2025: Snowflake CoWork (General availability)" sits at a...snowflake-intelligence.mdpath. (release-notes index; Feb 25, 2026 GA note) - Corroboration only, not a finding. A Japanese practitioner write-up independently shows
CREATE SNOWFLAKE INTELLIGENCEandALTER SNOWFLAKE INTELLIGENCE ... ADD AGENTrun in a real account and confirms theSNOWFLAKE_INTELLIGENCE.AGENTSschema migration path. Treated as a lead that the keyword is genuinely live, never as the evidence for it. (classmethod)
Convergences and contradictions
- Convergence, strongly. The parent brief's inference that a DDL rename "would need a behavior-change bundle and we found none" is now verified against the full 2026 bundle set plus the unbundled list, plus three documented precedents showing Snowflake really does use that channel for identifier renames. The parent brief's cautious guess is now a well-evidenced negative.
- Correction to a secondary source. A search summary encountered during this run asserted that the old view's reference page "still exists" and that the new page adds
PARENT_REQUEST_IDandUSER_NAME. Both claims are wrong. The old URL returns HTTP 308 and the search index is simply stale, and the archived March capture shows both columns already present. This is the exact trap the parent brief half-fell into when it read the alias sentence out of a search snippet. Search snippets of Snowflake docs in this product area are unreliable and must not be cited. - A separate deprecation exists nearby and must not be conflated with a rename. Current docs state the
SNOWFLAKE_INTELLIGENCE.AGENTSschema is deprecated as a mechanism for managing agent visibility, with a recommended migration to the Snowflake Intelligence object. That deprecation runs the opposite direction from a rename: it moves clients toward an object whose DDL keyword is the old name. Anyone skimming for the word "deprecated" in this doc set will find this and mis-report it as evidence the old name is going away. - One thing docs cannot settle. Whether the identifier
SNOWFLAKE_INTELLIGENCE_USAGE_HISTORYstill resolves in a live account is unanswerable from documentation. Snowflake documented neither an alias nor a removal. See the test-plan line under Open follow-ups.
Synthesis for RDCO
The useful finding is that the three layers moved at three different speeds, and the layer most likely to be in a client runbook is the layer that did not move at all. Snowflake's rename propagated through a documentation substitution variable, which is visible in the raw Markdown as an unresolved %sf-intelligence% token still carrying the old name as its variable key. That mechanism rewrites prose, page titles and even historical release-note headlines in one pass. It cannot touch a SQL identifier, because identifiers are literal text in code blocks and literal grammar in the engine. So the marketing layer flipped completely, the prose around the SQL flipped completely, and the SQL itself flipped only where someone edited a code block by hand. The view name and three of its columns got that hand edit. The DDL keyword, the object type, the three privilege names, the budget domain literal, the SERVICE_TYPE and ENTITY_TYPE values, the tag level enum, and two account-parameter values did not.
For the Principal/PM-track consulting work this matters in a specific and slightly counterintuitive way: the GRANT scripts are fine and should be left alone. A runbook that says GRANT USAGE ON SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT TO ROLE ... is quoting today's documentation correctly. Rewriting it to a CoWork spelling would produce a script that fails, and would be the worse error of the two. The defensible migration note is narrow: it goes on cost-monitoring and chargeback queries, where the view name changed and SNOWFLAKE_INTELLIGENCE_ID, SNOWFLAKE_INTELLIGENCE_NAME and SNOWFLAKE_INTELLIGENCE_TAGS became SNOWFLAKE_COWORK_*. Those column renames break a SELECT list even in the generous case where the view name still aliases, which makes them the one unambiguous action item in the whole question.
The behavior-change answer is worth carrying with real confidence because it was tested the right way. Snowflake has a documented channel for SQL-identifier renames and has used it repeatedly, including for a privilege rename and a column rename in output. Nothing about this object sits in any 2026 bundle or in the unbundled list. Combined with the policy's minimum eight weeks of admin-controlled testing and opt-out, and with 2026_08 being the newest bundle, there is no path by which the SNOWFLAKE INTELLIGENCE keyword or object name becomes unusable before the 2027 bundle cycle. If and when it does go, the Code Bundles precedent is the likeliest shape: a published note saying the old statements continue to work and no migration is required.
There is one genuinely odd observation to hold loosely rather than act on. The view rename is the only identifier change in this area that shipped with neither a release note nor a bundle entry, while its direct sibling SNOWFLAKE_COCO_USAGE_HISTORY got a dated GA note. Either the engine still answers to both names, which would make the doc change non-breaking and the missing paperwork correct, or a breaking ACCOUNT_USAGE change shipped outside Snowflake's own stated process. That ambiguity is the reason the view-name half of the recommendation is held at medium confidence while the keyword half is high. It is also a small, concrete credibility artifact: noticing that a vendor's rename skipped its own change-management channel is the kind of observation that earns trust in a discovery conversation, and it fits the agents-in-production domain the founder is building credibility in.
Recommendation: Add a migration note to client cost-monitoring and chargeback queries only, covering the view rename plus the three SNOWFLAKE_INTELLIGENCE_* to SNOWFLAKE_COWORK_* column renames, and explicitly leave DDL and GRANT scripts naming SNOWFLAKE INTELLIGENCE unchanged with a dated line saying why. Confidence: high on leaving DDL and GRANT scripts alone and on no scheduled retirement; medium on the view-name half, which needs one live query to settle.
Why this is in the vault
It closes the first open follow-up of [[2026-09-15-snowflake-intelligence-vs-cowork-naming-standard]] and converts that brief's "don't assume the old view still works" warning into an actionable, dated split: patch usage queries, leave grants alone. It is the citation a phData client runbook or SOW reviewer needs when asked why a 2026 deliverable still writes SNOWFLAKE INTELLIGENCE in SQL while writing "Snowflake CoWork" in prose.
Open follow-ups
- Snowflake renamed an ACCOUNT_USAGE view and three of its columns with no release note and no behavior-change bundle entry, while its sibling CoCo view got a dated GA note. Does Snowflake's behavior-change policy actually exempt ACCOUNT_USAGE view and column renames from the bundle process, or was this an unannounced exception? The policy page describes scope in general terms and never names ACCOUNT_USAGE. Resolving this determines whether we can trust bundle silence as a safety signal for ACCOUNT_USAGE identifiers generally, which affects every cost-monitoring deliverable, not just this one.
- The
SNOWFLAKE_INTELLIGENCE.AGENTSschema is deprecated as an agent-visibility mechanism with no published end-of-support date, and agents registered there are documented to keep working. What is the actual sunset commitment, and does that deprecation carry a bundle entry we should be tracking? This is the real migration exposure in this product area, and it is a genuinely different question from the naming one. - Snowflake's docs build renders the product name from a substitution variable whose key is still
sf-intelligence, which is why%sf-intelligence%leaks into the raw Markdown of current pages. Where else does unresolved or stale substitution leave the docs internally inconsistent in Cortex and CoWork pages, and is there a systematic way to detect it? Mis-set variables are a class of doc defect we have now hit twice in this product, and treating docs as a primary source means knowing their failure modes.
Test plan, not a research question: one statement, SELECT 1 FROM SNOWFLAKE.ACCOUNT_USAGE.SNOWFLAKE_INTELLIGENCE_USAGE_HISTORY LIMIT 1, settles whether the old view name still resolves; a successful run should be followed by DESCRIBE to see which column spellings that name returns. Stating this explicitly because it is not researchable: it needs a live Snowflake account with ACCOUNT_USAGE access, which we may not have, so it belongs to whoever next has a client or trial account in hand rather than to the research queue.
Related
- [[2026-09-15-snowflake-intelligence-vs-cowork-naming-standard]]
- [[2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix]]
- [[2026-07-08-cortex-agent-cowork-skill-native-publish]]
- [[2026-09-13-cortex-code-client-deployable-surface-p3-p4]]
- [[2026-07-07-snowflake-intelligence-vs-cortex-ai-boundary]]
- [[2026-10-02-snowflake-semantic-views-cortex-gateway-agent-identity-audit]]
- [[2026-11-05-snowflake-cortex-training-preview-status]]
Sources
Vault:
- 06-reference/research/2026-09-15-snowflake-intelligence-vs-cowork-naming-standard.md
- 06-reference/research/2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix.md
- 06-reference/research/2026-07-08-cortex-agent-cowork-skill-native-publish.md
- 06-reference/research/2026-09-13-cortex-code-client-deployable-surface-p3-p4.md
- 06-reference/research/2026-07-07-snowflake-intelligence-vs-cortex-ai-boundary.md
- 06-reference/research/2026-10-02-snowflake-semantic-views-cortex-gateway-agent-identity-audit.md
- 06-reference/research/2026-11-05-snowflake-cortex-training-preview-status.md
Web, primary (Snowflake documentation, all retrieved 2026-11-08):
- SNOWFLAKE_COWORK_USAGE_HISTORY view, ACCOUNT_USAGE: https://docs.snowflake.com/en/sql-reference/account-usage/snowflake_cowork_usage_history_view
- SNOWFLAKE_COWORK_USAGE_HISTORY view, ORGANIZATION_USAGE: https://docs.snowflake.com/en/sql-reference/organization-usage/snowflake_cowork_usage_history
- ACCOUNT_USAGE view reference and its deprecation labelling convention: https://docs.snowflake.com/en/sql-reference/account-usage
- ACCOUNT_USAGE complete page index (194 pages): https://docs.snowflake.com/en/sql-reference/account-usage/llms.txt
- ORGANIZATION_USAGE complete page index: https://docs.snowflake.com/en/sql-reference/organization-usage/llms.txt
- SQL Commands complete page index (778 pages; no entry for this object type): https://docs.snowflake.com/en/sql-reference/sql/llms.txt
- User access and settings for agents (CREATE/ALTER/SHOW and the three privileges): https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/deploy-agents
- Getting started with Snowflake CoWork (CREATE and GRANT USAGE): https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/getting-started
- Resource budgets for Snowflake CoWork (ALTER SNOWFLAKE INTELLIGENCE ... SET TAG): https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/cowork-resource-budgets
- Snowflake CoWork shared resource budgets (the 'SNOWFLAKE INTELLIGENCE' domain literal, SERVICE_TYPE, ENTITY_TYPE): https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/cowork-shared-budgets
- Behavior change announcements (bundle 2026_08 pending, 2026_07 enabled by default): https://docs.snowflake.com/en/release-notes/behavior-changes
- Behavior change bundles 2026_01 through 2026_08 (each retrieved and searched; zero hits): https://docs.snowflake.com/en/release-notes/bcr-bundles/2026_08_bundle
- Unbundled behavior changes (four CoWork entries, all behavioral; Code Bundles rename precedent): https://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/unbundled-behavior-changes
- Behavior change policy (eight-week testing and opt-out window): https://docs.snowflake.com/en/release-notes/behavior-change-policy
- Bundle 2025_03, CREATE DATA EXCHANGE LISTING renamed to CREATE LISTING (identifier-rename precedent): https://docs.snowflake.com/en/release-notes/bcr-bundles/2025_03/bcr-1926
- Release-notes complete index (no dated note for the CoWork view; dated note for the CoCo view): https://docs.snowflake.com/en/release-notes/llms.txt
- Feb 25, 2026 GA note, still titled with the old view name: https://docs.snowflake.com/en/release-notes/2026/other/2026-02-25-snowflake-intelligence-usage-history-view
- Feb 18, 2026 preview note for the old view: https://docs.snowflake.com/en/release-notes/2026/other/2026-02-18-snowflake-intelligence-usage-history-view
Web, archived primary (dated capture of Snowflake documentation):
- Internet Archive capture of the pre-rename view page, 2026-03-09, showing SNOWFLAKE_INTELLIGENCE_ID / _NAME / _TAGS: https://web.archive.org/web/20260309185245/https://docs.snowflake.com/en/sql-reference/account-usage/snowflake_intelligence_usage_history_view
Web, corroboration only (not used as the finding):
- classmethod, migrating agents from the SNOWFLAKE_INTELLIGENCE.AGENTS schema to the account-level object (Japanese; practitioner report): https://dev.classmethod.jp/articles/snowflake-intelligence-schema-migrate-to-account-object/