Snowflake vs BigQuery

Agent ops

1. ai-native userMy agent can run governed SQL end to end — authenticate, discover schemas, query, and read results back through a CLI or API with no dashboard in the loop

   weight 3 · round drawn
   Snowflake✓fullprobed8/10

   Snowflake provides multiple governed, non-dashboard paths for an agent to run SQL end-to-end: the SQL API (REST) for authenticating and executing queries/managing objects, the Snowflake CLI for programmatic access, RBAC/access history for governance, and a Snowflake-managed MCP server that lets agents securely retrieve data and execute SQL as tools without deploying infrastructure. missing for 10: independent/hands-on third-party validation of the full agent workflow (auth→discover→query→read-results) via CLI/API/MCP, and explicit documentation of schema-discovery APIs (e.g., information_schema access) tied directly to the MCP/SQL API flow.

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access History in Snowflake refers to when the user query reads data and when the SQL statement performs a data write operation... The user …”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”
   • [probe] “official CLI documented at https://docs.snowflake.com/en/developer-guide/snowflake-cli/index”

   proof ↗⚑ flag

   BigQuery✓fullprobed8/10

   BigQuery ships a documented, non-interactive bq CLI and a machine-readable REST API (verified live: keyless discovery doc exposes datasets/tables/routines/jobs resources) alongside IAM-based authentication/authorization, letting an agent authenticate, discover schemas, run SQL, and pull results with zero dashboard interaction. Google also ships an official MCP Toolbox with a prebuilt BigQuery toolset for agent access, confirmed running via npx (credential-gated as expected). Missing for 10: a first-party end-to-end hands-on trace showing an agent chaining auth to schema discovery to query to result-read purely via CLI/API without any human/dashboard step, and independent non-Google confirmation of this exact workflow.

   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”
   • [probe] “PROBE runtime (recorded 2026-09-06): Google's official MCP Toolbox for Databases ran from npm — `npx -y @toolbox-sdk/server --version` print…”
   • [probe] “official MCP server documented at https://github.com/googleapis/mcp-toolbox”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   proof ↗⚑ flag

2. ai-native userA built-in AI assistant writes, fixes, and explains SQL against my schemas from natural language, inside the product

   weight 2 · round to BigQuery
   Snowflake~partialclaimed7/10

   Cortex Analyst is a built-in, documented Snowflake feature that lets users ask questions in natural language and get answers 'without writing SQL,' implying it generates and runs SQL against the user's schema inside Snowsight; Cortex AI Functions and Notebooks further support SQL/Python assistance in-product. However, the evidence never explicitly shows the assistant 'fixing' or 'explaining' existing SQL (vs. generating it from scratch), and there's no independent/hands-on corroboration of accuracy or workflow beyond first-party docs. Missing for 10: explicit fix/explain-SQL capability documentation, and independent/community validation of the NL-to-SQL experience.

   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs from OpenAI, Anthropic, Met…”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs”
   • [claimed-docs] “Write SQL or Python code and quickly compare results with cell-by-cell development and execution.”
   • [claimed-docs] “Snowflake Notebooks is a unified development interface in Snowsight that offers an interactive, cell-based programming environment for Pytho…”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   Gemini in BigQuery provides an in-product natural-language assistant that generates/suggests SQL and Python code and explains existing queries, plus conversational analytics for chatting with data (docs-3,4,5,39,66,21,13). This matches the story of a built-in assistant writing, fixing, and explaining SQL from natural language directly inside the product. missing for 10: independent/hands-on user reports specifically validating the assistant's SQL-writing/fixing/explaining quality (only vendor docs cited).

   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”
   • [claimed-docs] “Conversational analytics now supports questions about market basket analysis.”

   proof ↗⚑ flag

3. ai-native userBusiness users can ask questions in natural language and get governed, semantically-grounded answers rather than hallucinated joins

   weight 1 · round to Snowflake
   Snowflake✓fullclaimed7/10

   Snowflake's Cortex Analyst is documented to let business users ask natural-language questions and get direct answers without writing SQL, and Snowflake Semantic Views let teams define business metrics/entities as governed semantic layer objects that Cortex Analyst can ground against, with RBAC controlling access to underlying data. This directly matches the story's ask for governed, semantically-grounded NL answers rather than raw hallucinated joins. missing for 10: independent/hands-on evidence validating accuracy or hallucination-reduction claims, and no detail on how Cortex Analyst explicitly enforces the semantic model to prevent bad joins (only first-party docs, no third-party corroboration).

   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object. You can define busines…”
   • [claimed-docs] “You can define business metrics and model business entities and their relationships.”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View ... define business metrics and model business entities…”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”

   proof ↗⚑ flag

   BigQuery~partialclaimed6/10

   BigQuery's Gemini-powered conversational analytics and data canvas explicitly let business users ask natural-language questions to find, join, and query tables, with collaboration and visualization built in (docs-3,4,5,39,66,13/21), and IAM-based access control (docs-31,65) provides a governance layer over which data can be queried. However, there's no first-party evidence of a dedicated semantic/business-glossary layer preventing hallucinated joins, and no independent or hands-on corroboration that these NL answers are reliably 'governed' or free of hallucination. Missing for 10: evidence of an explicit semantic modeling/metadata layer enforcing join correctness, and independent validation of answer accuracy/hallucination rates.

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”
   • [claimed-docs] “Conversational analytics now supports questions about market basket analysis.”
   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Snowflake
   Snowflake✓fullprobed9/10

   Snowflake publishes a root llms.txt (confirmed via live probe, HTTP 200) summarizing the platform, plus dedicated llms.txt files for individual products like Snowpark, Streamlit, and Snowflake Postgres, giving agents a structured, agent-oriented entry point into the docs. missing for 10: independent/third-party confirmation that agents successfully consume these llms.txt files in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.snowflake.com/llms.txt # Snowflake Documentation > Snowflake is a cloud data platform providing da…”
   • [claimed-docs] “Snowpark API for Python, Java, and Scala — process data at scale inside Snowflake.”
   • [claimed-docs] “Build and deploy interactive Streamlit apps directly inside Snowflake.”
   • [claimed-docs] “Managed Postgres instances running directly inside Snowflake.”

   proof ↗⚑ flag

   BigQuery—none0/10

   A direct probe for llms.txt at cloud.google.com returned 404, and no evidence pack item shows any agent-oriented docs manifest for BigQuery (only human-oriented docs pages in various languages).

   • [probe] “PROBE llms.txt: HTTP 404 at https://cloud.google.com/llms.txt”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Snowflake✓fullprobed8/10

   Snowflake ships an official CLI for managing apps/workloads and REST APIs (SQL API and Resource Management API) explicitly designed for programmatic, non-interactive integration and automation, which are the standard mechanisms for running Snowflake operations headlessly in CI pipelines. missing for 10: explicit CI/CD pipeline examples (e.g., GitHub Actions integration) and documentation of non-interactive auth flows (key-pair/OAuth) tailored for headless automation.

   • [claimed-docs] “With Snowflake CLI, developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflak…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [probe] “official CLI documented at https://docs.snowflake.com/en/developer-guide/snowflake-cli/index”

   proof ↗⚑ flag

   BigQuery✓fullprobed8/10

   BigQuery ships a documented Python-based CLI (`bq`) for scriptable dataset/table/query operations, a fully machine-readable REST API (verified live via discovery document), ODBC/JDBC drivers, and scheduled/batch load jobs — all standard building blocks for headless CI automation. missing for 10: explicit CI/CD pipeline examples (e.g. GitHub Actions/Cloud Build recipes) and independent hands-on reports of using bq/REST in automated pipelines.

   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Snowflake—none0/10

   Evidence documents Snowflake's own MCP server that exposes Snowflake's Cortex tools to external AI agents (server-side), but there is no evidence Snowflake can act as an MCP client consuming external MCP servers' tools to extend Cortex Agents or CoWork/CoCo's capabilities.

   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”

   proof ↗⚑ flag

   BigQuery—none0/10

   The evidence only shows Google's MCP Toolbox exposing BigQuery *as* an MCP server/tool provider for external AI agents (bigquery-probe-3, bigquery-probe-rt-2) — the opposite direction from this story, which asks whether a user can plug external MCP servers *into* BigQuery so BigQuery itself can consume their tools (e.g., within Gemini in BigQuery's conversational analytics). No evidence shows BigQuery or its Gemini features acting as an MCP client that ingests external tool servers.

   • [probe] “official MCP server documented at https://github.com/googleapis/mcp-toolbox”
   • [probe] “PROBE runtime (recorded 2026-09-06): Google's official MCP Toolbox for Databases ran from npm — `npx -y @toolbox-sdk/server --version` print…”
   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Snowflake
   Snowflake✓fullprobed9/10

   Snowflake documents an official, Snowflake-managed MCP server (Cortex Agents MCP) that lets AI agents securely retrieve data without deploying separate infrastructure, and it can be configured to serve Cortex Analyst, Cortex Search, Cortex Agents, custom tools, and SQL execution as MCP tools. This is a first-party, GA-documented feature confirmed by a direct probe of the docs URL. Missing for 10: independent/hands-on third-party corroboration of real-world agent connections beyond vendor docs.

   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”

   proof ↗⚑ flag

   BigQuery~partialprobed6/10

   Google's official MCP Toolbox for Databases (googleapis/mcp-toolbox) provides a documented, runnable MCP server with a prebuilt BigQuery toolset, confirmed to run via npx and require ADC credentials plus a project ID. However, it is a general 'Toolbox for Databases' rather than a BigQuery-specific first-party product page, and the runtime probe shows the handshake is credential-gated with no independent hands-on confirmation of full agent connectivity in production use. Missing for 10: independent/third-party corroboration of agent use, BigQuery-specific (not generic toolbox) branding, and evidence of production-scale reliability or broader ecosystem adoption.

   • [probe] “official MCP server documented at https://github.com/googleapis/mcp-toolbox”
   • [probe] “PROBE runtime (recorded 2026-09-06): Google's official MCP Toolbox for Databases ran from npm — `npx -y @toolbox-sdk/server --version` print…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Snowflake✓fullprobed8/10

   Snowflake ships an official Snowflake CLI documented for creating, managing, updating, and viewing apps across Streamlit, Native Apps, Snowpark Container Services, and Snowpark, confirmed by a dedicated docs probe. It's a general developer CLI rather than one purpose-built for AI-native/agentic workflows specifically. Missing for 10: independent/hands-on corroboration of CLI usage, and explicit agentic-workflow-specific CLI features (vs. general app management).

   • [claimed-docs] “With Snowflake CLI, developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflak…”
   • [claimed-docs] “developers can create, manage, update, and view apps running on Snowflake across workloads”
   • [claimed-docs] “developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflake, the Snowflake Nat…”
   • [probe] “official CLI documented at https://docs.snowflake.com/en/developer-guide/snowflake-cli/index”

   proof ↗⚑ flag

   BigQuery✓fullprobed8/10

   BigQuery ships 'bq', an official Python-based CLI for creating datasets, loading data, and querying tables, well documented across multiple doc pages and confirmed as a distinct probe finding. This is a general-purpose CLI rather than one purpose-built for AI-native agentic workflows (e.g., no agent-specific CLI features), so missing for 10: evidence of AI-agent-specific CLI features or tooling, independent hands-on community validation of CLI usage in agentic contexts.

   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “you learn how to use `bq`, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query …”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Snowflake✓fullprobed8/10

   Snowflake documents a public REST API for resource management and a SQL API (both OpenAPI-compliant with an official spec repo and Postman collections) allowing programmatic querying, deployment management, and integration building, plus Snowpark APIs for Python/Java/Scala. This is well-documented first-party evidence of a documented public API surface usable by AI-native/automated clients. Missing for 10: independent hands-on developer corroboration of API robustness/limits, and a discoverable machine-readable openapi.json at the probed standard paths (probe returned 404s despite claims of OpenAPI compliance).

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   BigQuery✓fullprobed8/10

   BigQuery exposes a documented, machine-readable REST API (v2 discovery doc confirmed live with resources for datasets/jobs/models/tables), plus gRPC Storage Write API, client SDKs, ODBC/JDBC drivers, and a Python-based bq CLI, all publicly documented and independently verified via runtime probe. missing for 10: no llms.txt or standalone OpenAPI spec file was found (404s), and the MCP server integration requires credential-gated setup rather than being fully turnkey.

   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”
   • [claimed-docs] “The Storage Write API (gRPC) has lower pricing and more robust features, including exactly-once delivery semantics.”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”
   • [probe] “PROBE llms.txt: HTTP 404 at https://cloud.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://cloud.google.com/openapi.json, https://cloud.google.com/swagger.json, https://cloud.google.c…”
   • [probe] “PROBE runtime (recorded 2026-09-06): Google's official MCP Toolbox for Databases ran from npm — `npx -y @toolbox-sdk/server --version` print…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Snowflake~partialclaimed5/10

   Snowflake's RBAC system lets admins scope privileges to specific roles that can then be attached to service/API credentials, and its REST APIs plus the Cortex Agents MCP server explicitly support secure, credential-based programmatic access for AI agents. However, no evidence directly documents an agent-specific credential-issuance workflow (e.g., short-lived scoped tokens purpose-built for agent identities) — the story is inferred from general RBAC/API docs rather than an agent-specific credentialing feature. Missing for 10: explicit documentation of issuing least-privilege, agent-scoped API keys/tokens (vs. general RBAC/roles), and any hands-on/independent confirmation of this workflow.

   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to”

   proof ↗⚑ flag

   BigQuery~partialclaimed5/10

   BigQuery documents predefined IAM roles/permissions scoped to specific resources (datasets, tables, views, routines) and custom quotas, which are the building blocks for issuing least-privilege access to any caller including an agent, but there is no explicit documentation of a workflow for minting scoped/short-lived API credentials specifically for an AI agent (e.g., service account impersonation, workload identity federation, or OAuth scope restriction guidance tied to agentic use). Missing for 10: explicit agent-credential-issuance guidance, short-lived/ephemeral token support, workload identity federation docs, and IAM Conditions examples for fine-grained scoping.

   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”
   • [claimed-docs] “複数の BigQuery プロジェクトとユーザーが存在している場合は、カスタム割り当てを要求することで費用を管理できます。この割り当てでは、1 日に処理されるデータ量の上限を指定します。”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Snowflake✓fullprobed7/10

   Snowflake documents multiple official SDKs/APIs for developers—Snowpark API for Python, Java, and Scala, the Snowflake SQL API, and REST APIs for resource management with OpenAPI specifications hosted in an official GitHub repo—plus a managed MCP server letting AI agents interact with Snowflake without custom infrastructure, directly supporting AI-native build patterns. Missing for 10: independent/hands-on developer corroboration of SDK quality/ergonomics and more explicit agent-framework integration examples beyond MCP.

   • [claimed-docs] “Snowpark API for Python, Java, and Scala — process data at scale inside Snowflake.”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”

   proof ↗⚑ flag

   BigQuery✓fullprobed7/10

   BigQuery documents multiple official SDK/API surfaces for building integrations: the Storage Write API (gRPC) client, a Rust SDK now in Preview, ODBC/JDBC drivers, the Python-based bq CLI, and a machine-readable REST v2 discovery document verified reachable keylessly at runtime. This gives an AI-native builder concrete, documented, and runtime-verified official surfaces to build against. Missing for 10: explicit listing/mention of mainstream language client libraries (Python, Java, Node.js, Go, .NET) by name and any independent hands-on developer report confirming SDK ergonomics beyond docs.

   • [claimed-docs] “The Rust SDK for BigQuery is now in Preview.”
   • [claimed-docs] “The Rust SDK for BigQuery is now in Preview”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”
   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Snowflake—none0/10

   Evidence shows Snowflake supports streams for CDC (polled) and notification integrations for cost alerts, but there is no documentation of a general-purpose webhook subscription mechanism that lets an AI-native user subscribe to events pushed via webhooks. Absence of evidence for this applicable capability yields 'none'.

   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “Notification integrations for cost anomaly alerts (General availability)”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables... so that actions can be taken using the changed data”

   proof ↗⚑ flag

   BigQuery—none0/10

   The evidence pack shows BigQuery streaming ingestion via Pub/Sub subscriptions and continuous queries for real-time analysis of incoming data, but nothing documents an outbound webhook mechanism for subscribing external clients to BigQuery events (e.g., job completion, table changes) via HTTP callbacks. Pub/Sub subscriptions described here are for loading data in, not for AI-native agents subscribing to events out.

   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub.”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Snowflake✓fullclaimed8/10

   Snowflake ships Cortex AI Functions for LLM-powered unstructured analytics on data in-place, and Cortex Analyst lets business users ask natural-language questions and get direct answers without SQL, plus semantic views to ground these insights in business context — all inside the product. missing for 10: independent/hands-on validation of insight quality and no evidence of proactive/automated suggestion surfacing (e.g., anomaly-based recommendations) beyond query-driven Q&A.

   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs from OpenAI, Anthropic, Met…”
   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object. You can define busines…”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View ... define business metrics and model business entities…”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery's Gemini integration provides conversational analytics (natural language Q&A over data), data canvas for exploration, SQL/Python code generation and query explanation, plus AI functions for summarization/sentiment/enrichment and BigQuery ML predictive insights — directly matching the story of in-product AI-generated insights and suggestions. missing for 10: independent/hands-on community validation of Gemini-in-BigQuery's actual output quality (only first-party docs cited) and more detail on proactive 'suggestions' beyond query generation.

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “Conversational analytics now supports questions about market basket analysis.”
   • [claimed-docs] “Train, evaluate, and deploy predictive analytics models directly within BigQuery using SQL.”
   • [claimed-docs] “Build sophisticated context-retrieval and RAG applications with embeddings and vector, text, or hybrid search to find information based on m…”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “Use generative AI in your workflows with AI functions for text summarization, sentiment analysis, and data enrichment.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Snowflake~partialclaimed5/10

   Snowflake documents several building blocks for background automation — Snowpipe auto-ingests files without manual scheduling, Dynamic Tables (GA) auto-refresh on a target lag, Streams capture DML changes to trigger downstream actions, and dbt Projects on Snowflake supports full orchestration of pipelines inside the platform. Cortex Agents plus the managed MCP server let AI agents query Snowflake data, but the evidence shows MCP as a request/response tool-serving interface rather than a documented mechanism for an AI-native user to schedule agents that run continuously and autonomously in the background. Missing for 10: explicit documentation of a Tasks/scheduler feature for autonomous job execution, evidence of agent-triggered/looping automations (not just query-based interactions), and independent/hands-on confirmation that these pieces compose into unattended AI-driven automation.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “CREATE OR ALTER DYNAMIC TABLE (General availability)”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   BigQuery~partialclaimed5/10

   BigQuery offers background-automation primitives — continuous queries that run indefinitely to process streaming data in real time, scheduled load jobs, and Dataform for scheduling and orchestrating multi-step transformation workflows — which can run autonomously without a user actively invoking them. However, none of this is framed or documented as 'AI-native' agentic automation (e.g., AI-triggered actions, agent orchestration, or autonomous decision loops using BigQuery's AI/ML functions), and there is no independent/community corroboration of these automation features being used this way. Missing for 10: AI-agent-specific automation/orchestration evidence, independent hands-on validation of continuous queries/Dataform running unattended long-term, and any framing tying automation to autonomous AI workflows rather than plain data-pipeline scheduling.

   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “View a visualization of the dependency tree of your workflow.”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to BigQuery
   Snowflake~partialclaimed4/10

   Snowflake's homepage advertises 'Snowflake CoWork' ('Ask anything') and 'Snowflake CoCo' ('Build anything') as built-in enterprise AI assistants, and Cortex Analyst lets business users get natural-language answers without SQL — both suggest task delegation to an in-product assistant. However, the evidence pack has no dedicated docs page, feature list, or independent/hands-on account of CoWork/CoCo's actual task-delegation capabilities, so the claim rests on thin marketing taglines rather than substantiated documentation. Missing for 10: dedicated CoWork/CoCo documentation detailing task-delegation scope, hands-on or independent corroboration of the assistant performing multi-step tasks, and clarity on how it differs from Cortex Analyst's NL query feature.

   • [claimed-docs] “Ask anything with Snowflake CoWork. Build anything with Snowflake CoCo. Welcome to your one-stop shop for everyone in the enterprise.”
   • [claimed-docs] “Build anything with Snowflake CoCo.”
   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”

   proof ↗⚑ flag

   BigQuery✓fullclaimed7/10

   BigQuery ships Gemini in BigQuery, a built-in AI assistant offering conversational analytics (natural-language Q&A over data), a data canvas for exploring/transforming/querying/visualizing data, and SQL/Python code generation, explanation, and suggestion — directly matching the story of delegating tasks to an in-product AI assistant. Release notes also show ongoing expansion (e.g., market basket analysis support in conversational analytics). missing for 10: independent/hands-on user reports validating Gemini in BigQuery's assistant behavior (only first-party docs cited), and no evidence of broader agentic task delegation (e.g., multi-step autonomous execution) beyond query/code assistance.

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “Conversational analytics now supports questions about market basket analysis.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Snowflake~partialclaimed7/10

   Snowflake documents genuine natural-language operation via Cortex Analyst (ask business questions in NL, get answers without writing SQL) and Cortex AI Functions for NL-driven analytics on text/images, plus a marketed 'CoWork'/'CoCo' NL agent interface and an MCP server exposing these NL/agent capabilities to external AI agents. This is solid support for AI-native NL interaction, but most of it is scoped to querying/analytics rather than full product administration (warehouses, security, pipelines) via natural language, and CoWork/CoCo are only marketing taglines with no detailed docs in the pack. Missing for 10: independent/hands-on validation of NL breadth, detailed CoWork/CoCo documentation, and evidence that operational/admin tasks (not just analytics) can be driven by natural language.

   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs from OpenAI, Anthropic, Met…”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs”
   • [claimed-docs] “Ask anything with Snowflake CoWork. Build anything with Snowflake CoCo. Welcome to your one-stop shop for everyone in the enterprise.”
   • [claimed-docs] “Build anything with Snowflake CoCo.”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   BigQuery~partialclaimed7/10

   BigQuery's Gemini/Conversational Analytics features let users query, join, and visualize data using natural language, and generate/explain SQL or Python code from NL prompts, which directly supports natural-language operation of the product. However, this is all first-party doc-based evidence with no independent/hands-on corroboration, and NL support seems scoped to querying/exploration rather than full operational control (e.g., admin, pipeline management). Missing for 10: independent verification of NL feature reliability, evidence of NL commands controlling broader BigQuery operations beyond analytics/query generation.

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “Conversational analytics now supports questions about market basket analysis.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Snowflake
   Snowflake~partialprobed3/10

   Snowflake publishes OpenAPI-compliant spec files and importable Postman collections for its REST/SQL APIs, which gives developers a way to run example requests, but there is no evidence of an embedded, interactive 'try-it' API reference on the docs site itself — a direct probe for openapi.json/swagger endpoints returned 404s. Missing for 10: an in-browser interactive API explorer (e.g., Swagger/Redoc UI) hosted by Snowflake, and any independent confirmation that the Postman-based workflow is commonly used as a live API reference.

   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   BigQuery—none0/10

   The evidence shows only a machine-readable REST discovery document (bigquery-probe-rt-1) and standard docs pages, with explicit probe failures for llms.txt and openapi.json (bigquery-probe-1, bigquery-probe-2). There is no evidence of an interactive, runnable-example API reference (e.g., a try-it console or embedded runnable code snippets) for AI-native exploration.

   • [probe] “PROBE llms.txt: HTTP 404 at https://cloud.google.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://cloud.google.com/openapi.json, https://cloud.google.com/swagger.json, https://cloud.google.c…”
   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Snowflake
   Snowflake✓fullprobed8/10

   Snowflake publishes an official, first-party GitHub repository (snowflakedb/snowflake-rest-api-specs) containing downloadable OpenAPI-compliant spec files plus Postman collections for its REST APIs, and its own docs explicitly state the REST APIs are 'compliant with the OpenAPI specification' and enable building integrations 'using the openAPI specifications.' Missing for 10: a directly hosted /openapi.json or /swagger.json endpoint on the docs site itself (probe found 404s there), so the machine-readable spec must be fetched from the separate GitHub repo rather than a single canonical URL.

   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   BigQuery~partialprobed6/10

   BigQuery does not host a standard OpenAPI/swagger.json file (probe confirms openapi.json/swagger.json paths 404), but it exposes Google's own machine-readable API Discovery Document (bigquery:v2) at the REST reference which was verified to download keylessly and parse cleanly into resources/methods — functionally equivalent to an OpenAPI spec though in a different format. Missing for 10: a canonical OpenAPI/Swagger file, first-party statement equating the Discovery doc to OpenAPI, and independent community confirmation of AI-native tooling consuming it.

   • [probe] “PROBE openapi: all candidate paths 404 (https://cloud.google.com/openapi.json, https://cloud.google.com/swagger.json, https://cloud.google.c…”
   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to BigQuery
   Snowflake~partialclaimed5/10

   Snowflake's zero-copy cloning (object-clone) lets users create full database/schema clones inheriting privileges without duplicating or altering production data, which supports building an isolated sandbox for testing, and RBAC plus resource monitors help isolate/limit that environment. However, the evidence never frames this explicitly as an 'AI-native sandbox' workflow or ties cloning to agentic/AI testing use cases. missing for 10: explicit sandbox/dev-test documentation framed for AI-native or agent workflows, guidance on isolating agent test runs from prod data, and independent corroboration of clone-based sandboxing in practice.

   • [claimed-docs] “the clone inherits all granted privileges on the clones of all child objects contained in the source object”
   • [claimed-docs] “If the source object is a database or schema, the clone inherits all granted privileges on the clones of all child objects contained in the …”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”

   proof ↗⚑ flag

   BigQuery✓fullclaimed7/10

   BigQuery Sandbox is explicitly documented as a way to explore and test BigQuery capabilities without a billing account or credit card, functioning as an isolated environment separate from a paid production setup. This directly matches the story of testing without touching production data, though evidence is purely first-party docs. Missing for 10: independent/hands-on confirmation of sandbox isolation guarantees, and specifics on how sandbox environments map to keeping AI-agent test workloads fully separate from production datasets.

   • [claimed-docs] “Mit der BigQuery-Sandbox können Sie BigQuery nutzen, ohne eine Kreditkarte anzugeben oder ein Rechnungskonto für Ihr Projekt zu erstellen.”
   • [claimed-docs] “The BigQuery sandbox lets you explore limited BigQuery capabilities at no cost to confirm whether BigQuery fits your needs.”
   • [claimed-docs] “The BigQuery sandbox lets you experience BigQuery without providing a credit card or creating a billing account for your project.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Snowflake
   Snowflake~partialclaimed6/10

   Snowflake documents official REST APIs (SQL API, resource-management API) built on OpenAPI specs, and maintains a dedicated 'Behavior change announcements' page describing dated bundles of changes meant to minimize disruption — functioning as a de facto deprecation/change policy. However, there's no explicit documentation of API version numbers (v1/v2) or formal deprecation timelines/sunset dates for the APIs themselves. Missing for 10: explicit API versioning scheme documentation, formal deprecation timeline/sunset policy tied to specific API versions, independent corroboration of API stability guarantees.

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “Docs, "Behavior change announcements": "To help you manage your operations and minimize disruption to your Snowflake service, we document be…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”

   proof ↗⚑ flag

   BigQuery~partialprobed4/10

   BigQuery exposes a versioned, machine-readable REST API (v2 discovery document) confirmed via runtime probe, showing a genuine versioned API surface, but there is no evidence in the pack of a documented deprecation policy, versioning cadence, or sunset guarantees for that API. missing for 10: explicit deprecation/sunset policy docs, versioning changelog commitments, and independent confirmation of long-term API stability guarantees.

   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”
   • [claimed-docs] “The Rust SDK for BigQuery is now in Preview.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to BigQuery
   Snowflake~partialclaimed6/10

   Snowflake supports bulk/batch operations via SQL (COPY INTO, Snowpipe micro-batches), Snowpark for programmatic bulk data processing, REST/SQL APIs for scripted batch operations, and CLI/dbt for orchestrating multi-object workflows, but these are general data-platform bulk operations rather than an AI-native agent-oriented bulk-action capability explicitly designed for AI agents to invoke across many items at once. The MCP server (Cortex Agents MCP) exposes tools for agents but evidence doesn't show explicit bulk/batch operation support through that interface. missing for 10: explicit documentation of AI-agent-initiated bulk operations (e.g., MCP server batch tool calls across many items), hands-on/independent evidence of AI-native bulk workflows succeeding at scale, and any agent-specific bulk-action API beyond generic SQL/REST batch capabilities.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowpark API for Python, Java, and Scala — process data at scale inside Snowflake.”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   BigQuery✓fullcommunity7/10

   BigQuery natively supports bulk operations via DML for batch insert/update/delete, batch load jobs with scheduling, and the high-throughput Storage Write API for large-scale bulk ingestion, plus the bq CLI for scripting these operations across many items/tables. Community evidence corroborates BigQuery's ability to process petabyte-scale data efficiently. Missing for 10: explicit evidence of AI-agent-driven orchestration of bulk operations (e.g., an agent issuing many bulk actions via MCP/API in one flow) and independent benchmarks specifically on DML/bulk-write scale rather than just query scale.

   • [claimed-docs] “Data Manipulation Language (DML) statements enable you to update, insert, and delete data from your BigQuery tables.”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”
   • [claimed-docs] “the distributed and scalable analysis engine of BigQuery allows querying terabytes in seconds and petabytes in minutes”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Snowflake
   Snowflake~partialclaimed6/10

   Snowflake offers building blocks that support event-driven automation — Streams capture DML changes for downstream actions, Snowpipe auto-ingests new files, resource monitors can auto-suspend warehouses on cost thresholds, and anomaly monitors trigger notification alerts — but there is no single unified 'rules engine' or declarative trigger-action framework exposed as one product for AI-native users to define arbitrary event-condition-action automations. missing for 10: a first-class, general-purpose rules/trigger-action framework (e.g., 'if X event then do Y') rather than disparate feature-specific mechanisms (streams+tasks, Snowpipe, resource monitors), and independent/hands-on evidence of composing these into end-to-end automated workflows.

   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables... so that actions can be taken using the changed data”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage”
   • [claimed-docs] “You can use a resource monitor to monitor credit usage by virtual warehouses ... You can also set up a resource monitor to suspend a standar…”
   • [claimed-docs] “you can set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit limit”
   • [claimed-docs] “Anomaly monitors for cost anomalies (Preview)”
   • [claimed-docs] “Notification integrations for cost anomaly alerts (General availability)”

   proof ↗⚑ flag

   BigQuery~partialclaimed4/10

   BigQuery's continuous queries feature runs SQL statements continuously to analyze incoming data in real time, which is the closest capability to event-triggered automation, but there is no evidence of a general rules/condition-action engine that fires arbitrary actions (notifications, function calls, workflows) on events—continuous queries are limited to SQL-based streaming analysis. Missing for 10: explicit rule definition UI/API, broader action types (not just SQL output), and evidence of integration with external triggers/alerts as an automation mechanism.

   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to BigQuery
   Snowflake~partialclaimed4/10

   Evidence shows dbt Projects on Snowflake can 'orchestrate' transformations with a managed runtime, implying some recurring-job scheduling capability, but the pack contains no direct documentation of Snowflake's native TASK/scheduler object or agent-triggered recurring workflows for AI-native users. Missing for 10: explicit docs on Snowflake Tasks or a scheduler API, evidence of AI agents creating/managing recurring jobs via MCP or CLI, and independent/hands-on confirmation of scheduling reliability.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”

   proof ↗⚑ flag

   BigQuery✓fullclaimed7/10

   BigQuery documents native support for recurring automation: scheduled load jobs ('schedule one-time or batch data transfers at regular intervals') and Dataform for developing, testing, versioning, and scheduling complex data-transformation workflows, plus continuous queries for always-on real-time processing. These are first-party, concrete capabilities directly matching the story. Missing for 10: explicit mention of the dedicated BigQuery Scheduled Queries feature by name, and independent/hands-on confirmation of scheduling reliability in production.

   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “View a visualization of the dependency tree of your workflow.”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to BigQuery
   Snowflake~partialclaimed4/10

   Snowflake docs show building blocks that touch pieces of this story — dbt Projects on Snowflake covers the 'develop, deploy, orchestrate, observe' lifecycle (implying dbt's git-based versioning) [snowflake-docs-2][snowflake-docs-55], Time Travel lets you restore/rollback objects and query past states [snowflake-docs-5][snowflake-docs-24][snowflake-docs-35], and object cloning/behavior-change bundles give some notion of state snapshots and change tracking [snowflake-docs-67][snowflake-supp-behavior-changes]. However there is no dedicated, documented capability for versioning, reviewing, and rolling back 'automations' (e.g., Tasks, Dynamic Tables pipelines, agent workflows) as a first-class AI-native feature — the evidence is inferential rather than a direct product answer to this story. Missing for 10: explicit versioning/review/rollback tooling for Tasks/Dynamic Tables/agent pipelines, a documented approval/review workflow for automation changes, and independent/hands-on confirmation of rollback working for automations specifically.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted.”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted. You can restore individual objects, such as tables, or restore…”
   • [claimed-docs] “the clone inherits all granted privileges on the clones of all child objects contained in the source object”
   • [claimed-docs] “Docs, "Behavior change announcements": "To help you manage your operations and minimize disruption to your Snowflake service, we document be…”

   proof ↗⚑ flag

   BigQuery~partialclaimed5/10

   Dataform (BigQuery's workflow/transformation service) explicitly supports version control and Git-based collaboration for data pipelines, plus Git folders for scheduled pipelines, which cover versioning and team review to a degree. However, there's no explicit documentation of a rollback mechanism or formal review/approval workflow for automations beyond generic Git usage. Missing for 10: explicit rollback/revert documentation, structured review/approval process (e.g., PR-based approvals) for automations, and independent/hands-on evidence confirming these workflows in practice.

   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “View a visualization of the dependency tree of your workflow.”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”
   • [claimed-docs] “You can now create, store, and manage pipelines in Git folders.”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”

   proof ↗⚑ flag

Pricing

1. platform-engineerThe pricing model is documented clearly enough that I can estimate a monthly bill for my workload before committing

   weight 3 · round drawn
   Snowflake!disputedcontradicted5/10

   Snowflake docs explain the underlying cost model (credit-consuming virtual warehouses, resizing, resource monitors, cost-anomaly alerts, and a general pricing-tier page) which gives a platform engineer the mechanics needed to model cost, but there is no concrete rate card or calculator evidenced. Community reports concretely contradict the 'estimate before committing' claim: users note costs 'balloon pretty fast', warehouse credit consumption 'doubles each size up', there is 'no query level attribution of costs and no in-built features for monitoring', and it's 'easy... to get to $100k/year bills without massive data' — indicating the documented model is hard to translate into an accurate upfront estimate in practice. missing for 10: a transparent unit-price/rate table, a first-party cost calculator, and independent confirmation that engineers can reliably forecast bills from the docs alone.

   • [claimed-docs] “Virtual warehouses consume credits as they execute queries, load data and perform other DML operations. Virtual Warehouses are user-managed,…”
   • [claimed-docs] “Virtual Warehouses are user-managed, which means you can directly control credit consumption of these resources.”
   • [claimed-docs] “You can use a resource monitor to monitor credit usage by virtual warehouses ... You can also set up a resource monitor to suspend a standar…”
   • [claimed-docs] “you can set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit limit”
   • [claimed-docs] “An entry-level, introductory offering providing access to core functionality.”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”
   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”
   • [community] “The problem with Snowflake is particularly worse due to its lack of query level attribution of costs and no in-built features for monitoring…”
   • [community] “I have no Snowflake experience, but some limited BigQuery experience. And it's very easy for a small company to get to $100k/year bills with…”

   proof ↗⚑ flag

   BigQuery!disputedcontradicted5/10

   Google documents pricing clearly (on-demand per-TiB, first 1TiB free, slot-based flat-rate reservations, custom quotas to cap spend) and community reports confirm a dry-run/bytes-scanned estimator exists that lets users predict costs before running queries. However, a concrete hands-on report describes a user being billed $14,000 with zero warning, and community critique that BigQuery 'hides query cost behind abstracted TBs scanned or slots' making bill estimation harder than it should be — a direct contradiction to the claim that pricing is 'documented clearly enough to estimate a bill' in practice. missing for 10: independent case studies showing accurate monthly forecasting at scale, clearer treatment of storage/streaming/BI Engine cost interactions, and resolution of the surprise-billing complaint.

   • [claimed-docs] “On-demand pricing (per TiB). With this pricing model, you are charged for the number of bytes processed by each query. The first 1 TiB of qu…”
   • [claimed-docs] “BigQuery offers a choice of two compute pricing models for running queries”
   • [claimed-docs] “You can also reserve compute capacity ahead of time in the form of slots, which represent virtual CPUs.”
   • [claimed-docs] “複数の BigQuery プロジェクトとユーザーが存在している場合は、カスタム割り当てを要求することで費用を管理できます。この割り当てでは、1 日に処理されるデータ量の上限を指定します。”
   • [community] “User ran a script on BigQuery for HTTP Archive data and was billed $14,000 with zero warning; complained about lack of customer support and …”
   • [community] “BQ hides query cost behind abstracted 'TBs scanned' or 'slots' mechanism; if GCP returned query cost directly in API/console it would be muc…”
   • [community] “BigQuery provides a dry run option to estimate bytes/costs before running a query, and shows bytes-to-be-scanned in small text before you hi…”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”
   • [community] “BigQuery announced pricing changes: annual flat rate going from 2.3c to 4.8c per slot hour, and on-demand pricing increasing 25% (from $5/TB…”
   • [community] “BigQuery has on-demand pricing metered by data read, plus reserved slot pricing metered by time; reserved slots offer a considerable discoun…”

   proof ↗⚑ flag

2. platform-engineerBudgets, resource monitors, or auto-suspend stop a runaway query or idle compute from burning money overnight

   weight 2 · round to Snowflake
   Snowflake✓fullcommunity8/10

   Snowflake ships resource monitors that track credit usage and can auto-suspend a virtual warehouse (or disable an Adaptive Warehouse) when a threshold is hit, plus GA cost-anomaly monitors, per-user quotas, and notification integrations for cost alerts, directly matching the platform-engineer need to stop runaway spend. Community commentary independently corroborates this as standard practice (setting up resource monitors and using small warehouses to control cost), and warehouses can also be manually started, stopped, and resized to control burn. Missing for 10: independent hands-on confirmation that resource monitors reliably kill an in-flight runaway query versus only suspending future warehouse starts, and detail on statement-level timeout controls.

   • [claimed-docs] “You can use a resource monitor to monitor credit usage by virtual warehouses ... You can also set up a resource monitor to suspend a standar…”
   • [claimed-docs] “you can set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit limit”
   • [claimed-docs] “You can also set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit lim…”
   • [claimed-docs] “Per-user quotas (General availability)”
   • [claimed-docs] “Anomaly monitors for cost anomalies (Preview)”
   • [claimed-docs] “Notification integrations for cost anomaly alerts (General availability)”
   • [claimed-docs] “Virtual warehouses consume credits as they execute queries, load data and perform other DML operations. Virtual Warehouses are user-managed,…”
   • [claimed-docs] “Warehouses can be started and stopped at any time. They can also be resized at any time, even while running, to accommodate the need for mor…”
   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”

   proof ↗⚑ flag

   BigQuery!disputedcontradicted4/10

   BigQuery docs describe custom quotas that cap daily bytes processed per project/user as a cost-control mechanism, and community discussion confirms dry-run/bytes-scanned previews exist to estimate cost before running a query — but a documented real-world case shows a runaway query still resulted in a surprise $14,000 bill with 'zero warning' and Google refusing to waive it, meaning no automatic budget/resource-monitor/auto-suspend actually intervened. Missing for 10: evidence of real-time Cloud Billing budget alerts wired to auto-suspend BigQuery usage, a per-query 'maximum bytes billed' kill-switch, or any documented fix/response after the community-reported billing incident.

   • [claimed-docs] “複数の BigQuery プロジェクトとユーザーが存在している場合は、カスタム割り当てを要求することで費用を管理できます。この割り当てでは、1 日に処理されるデータ量の上限を指定します。”
   • [community] “User ran a script on BigQuery for HTTP Archive data and was billed $14,000 with zero warning; complained about lack of customer support and …”
   • [community] “BigQuery provides a dry run option to estimate bytes/costs before running a query, and shows bytes-to-be-scanned in small text before you hi…”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”

   proof ↗⚑ flag

Trial

1. analystEvaluate with a free tier or trial — real queries on real data without a credit card or a sales call

   weight 1 · round to BigQuery
   Snowflake~partialcommunity5/10

   Community evidence confirms a real, usable free trial exists (a user ran actual queries burning real credits and storage over the trial period), showing the trial supports real queries on real data — but there is no first-party documentation in the pack describing signup requirements (credit card, sales contact) for that trial, and pricing docs only describe a paid 'Standard' entry tier rather than a no-card free trial. missing for 10: official docs confirming no-credit-card signup, no sales-call requirement, and trial credit/duration terms.

   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”
   • [claimed-docs] “An entry-level, introductory offering providing access to core functionality.”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery Sandbox explicitly lets analysts explore BigQuery capabilities and run real queries without providing a credit card or creating a billing account, and on-demand pricing includes 1 TiB of free query processing per month — directly matching the story of a no-card, no-sales-call evaluation path. Missing for 10: independent/hands-on user reports confirming the sandbox experience in practice (only first-party docs are cited, and community evidence focuses on billing surprises for paid usage rather than the sandbox itself).

   • [claimed-docs] “Mit der BigQuery-Sandbox können Sie BigQuery nutzen, ohne eine Kreditkarte anzugeben oder ein Rechnungskonto für Ihr Projekt zu erstellen.”
   • [claimed-docs] “The BigQuery sandbox lets you explore limited BigQuery capabilities at no cost to confirm whether BigQuery fits your needs.”
   • [claimed-docs] “The BigQuery sandbox lets you experience BigQuery without providing a credit card or creating a billing account for your project.”
   • [claimed-docs] “On-demand pricing (per TiB). With this pricing model, you are charged for the number of bytes processed by each query. The first 1 TiB of qu…”

   proof ↗⚑ flag

Bi

1. analystStandard drivers (JDBC/ODBC) and documented BI-tool integrations connect my dashboards without custom glue

   weight 1 · round to BigQuery
   Snowflake—none0/10

   The evidence pack contains no specific mention of JDBC/ODBC drivers or documented BI-tool integrations (e.g., Tableau, Power BI, Looker) for Snowflake; only a generic reference to 'applications and tools you can use to access Snowflake' (snowflake-docs-27) without detail on standard drivers or BI connectors. This is an axis that clearly applies to a data warehouse product, but no concrete evidence demonstrates the capability.

   ⚑ flag

   BigQuery✓fullprobed9/10

   BigQuery documents official Simba JDBC and ODBC drivers explicitly for connecting BI tools and applications to BigQuery, plus native integrations (bq CLI, Sheets, Analytics Hub/sharing) that support dashboard connectivity without custom glue. Missing for 10: no independent hands-on report confirming smooth BI-tool dashboard connection experience beyond vendor docs.

   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   proof ↗⚑ flag

Dev loop

1. data-engineerI get a fast local or free dev loop — a local engine, emulator, or sandbox — to develop transformations before touching production compute

   weight 2 · round to BigQuery
   Snowflake—none0/10

   Snowflake's evidence pack covers cloud compute (warehouses, Snowpipe, notebooks, dbt-in-Snowflake, Snowpark) but nothing about a local engine, emulator, or free sandbox for developing transformations before touching production compute — everything described runs against live Snowflake compute/credits. Community evidence even notes trial credits get consumed quickly (~$19.60 in credits within days), reinforcing that there's no cost-free local dev loop. Missing for 10: any local engine/emulator, offline dev mode, or a genuinely free (non-credit-consuming) sandbox tier.

   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”
   • [claimed-docs] “An entry-level, introductory offering providing access to core functionality.”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”
   • [claimed-docs] “Virtual warehouses consume credits as they execute queries, load data and perform other DML operations. Virtual Warehouses are user-managed,…”

   proof ↗⚑ flag

   BigQuery~partialclaimed5/10

   BigQuery offers a free 'Sandbox' mode that lets users try queries and transformations without a credit card or billing account, and on-demand pricing gives 1 TiB/month free — both lowering the barrier to a free dev loop. However, there is no evidence of a local engine or offline emulator (unlike e.g. Firestore's emulator); the Sandbox is still a hosted, quota-limited slice of the real cloud service, not a local dev-loop tool. Missing for 10: a documented local/offline emulator, evidence of local development without any cloud dependency, and any hands-on account confirming the sandbox is sufficient for full transformation development before touching production.

   • [claimed-docs] “Mit der BigQuery-Sandbox können Sie BigQuery nutzen, ohne eine Kreditkarte anzugeben oder ein Rechnungskonto für Ihr Projekt zu erstellen.”
   • [claimed-docs] “The BigQuery sandbox lets you explore limited BigQuery capabilities at no cost to confirm whether BigQuery fits your needs.”
   • [claimed-docs] “The BigQuery sandbox lets you experience BigQuery without providing a credit card or creating a billing account for your project.”
   • [claimed-docs] “On-demand pricing (per TiB). With this pricing model, you are charged for the number of bytes processed by each query. The first 1 TiB of qu…”

   proof ↗⚑ flag

Transformation

1. data-engineerDbt is a first-class citizen — a documented adapter or native dbt project support with vendor docs to match

   weight 2 · round to Snowflake
   Snowflake✓fullcommunity8/10

   Snowflake has a dedicated first-party feature, 'dbt Projects on Snowflake,' with vendor docs describing native support for the full dbt lifecycle (develop, deploy, orchestrate, observe), managed dbt Core/Fusion runtimes, and a documented migration path from dbt Core. This goes beyond a community adapter — it's native, vendor-documented dbt support. missing for 10: independent/hands-on validation of dbt Projects on Snowflake in production, and more detail on parity/limitations vs dbt Core for advanced use cases.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “Migrating an existing dbt Core project? See the Migrate from dbt Core to dbt Projects on Snowflake.”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”
   • [community] “The issue with dbt models in Snowflake is that if you perform a full-refresh and don't sort it, you ruin any natural clustering from an incr…”

   proof ↗⚑ flag

   BigQuery—none0/10

   The evidence pack contains no vendor documentation from Google about a dbt adapter or native dbt project support for BigQuery; the only related item is a community comment casually noting BigQuery's pipe syntax is 'great for dbt macros,' which is a third-party observation, not vendor-documented adapter support. Absence of evidence for this applicable ecosystem-integration axis yields 'none.'

   • [community] “Review after a week of using BigQuery's new SQL pipe syntax: much more productive for data exploration/cleaning, unifies WHERE/HAVING/QUALIF…”

   proof ↗⚑ flag

Access

1. platform-engineerAccess control reaches tables, columns, and rows — roles plus masking policies — so one warehouse can serve many teams safely

   weight 3 · round drawn
   Snowflake~partialclaimed5/10

   Docs confirm Snowflake's core RBAC model (privileges assigned to roles, roles to users) and Access History views tracking table/column-level query and write activity, which supports auditing at the object level. However, the evidence pack contains no mention of dynamic data masking policies or row access policies (row-level security), which are the specific mechanisms the story calls out for column- and row-level control — missing for 10: masking policy documentation, row access policy documentation, and any independent/hands-on confirmation these work as described.

   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”
   • [claimed-docs] “Access History in Snowflake refers to when the user query reads data and when the SQL statement performs a data write operation... The user …”
   • [claimed-docs] “The records in these views facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and colu…”
   • [claimed-docs] “facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and columns”
   • [claimed-docs] “The user access history can be found by querying the ACCESS_HISTORY view in the ACCOUNT_USAGE and ORGANIZATION_USAGE schemas.”

   proof ↗⚑ flag

   BigQuery~partialprobed5/10

   IAM predefined roles for BigQuery resources (datasets, tables, views, routines) are documented, and the REST API surface exposes a rowAccessPolicies resource confirming row-level security exists, but the evidence pack contains no documentation of column-level access controls or masking policies (e.g., taxonomy-based dynamic data masking) needed to fully satisfy the story. missing for 10: column-level security/masking policy documentation, examples of combining row+column policies with IAM roles for multi-tenant governance, independent/hands-on corroboration of masking behavior.

   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”

   proof ↗⚑ flag

Governance

1. platform-engineerI get audit logs of who ran what and column-level lineage of where data came from

   weight 2 · round to Snowflake
   Snowflake~partialclaimed6/10

   Snowflake provides strong audit-log coverage via Query History (who ran what queries) and Access History (ACCESS_HISTORY view tracking reads/writes for compliance auditing, including per-column access insights), which addresses the 'who ran what' half of the story well. However, the evidence pack does not document an explicit column-level lineage graph/feature (e.g., Snowflake's Horizon/lineage explorer) showing upstream data provenance — only that Access History surfaces 'popular and frequently accessed tables and columns,' which is usage insight, not full lineage tracing. Missing for 10: explicit column-level lineage/graph documentation, independent validation of lineage accuracy across transformations.

   • [claimed-docs] “With the Query History page in Snowsight, you can do the following: Monitor individual or grouped queries that are executed by users in your…”
   • [claimed-docs] “The Query History page lets you explore queries executed in your Snowflake account over the last 14 days.”
   • [claimed-docs] “Access History in Snowflake refers to when the user query reads data and when the SQL statement performs a data write operation... The user …”
   • [claimed-docs] “The records in these views facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and colu…”
   • [claimed-docs] “The user access history can be found by querying the ACCESS_HISTORY view in the ACCOUNT_USAGE and ORGANIZATION_USAGE schemas.”
   • [claimed-docs] “facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and columns”

   proof ↗⚑ flag

   BigQuery—none0/10

   The evidence pack only covers IAM roles/permissions (bigquery-docs-31, bigquery-docs-65) and compliance certifications, with no mention of Cloud Audit Logs, job history, or column-level lineage tracking (e.g., Data Catalog/Dataplex lineage) for BigQuery. Governance/audit-and-lineage is a plausible and expected axis for a data warehouse, but no evidence in this pack substantiates it.

   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”

   proof ↗⚑ flag

2. platform-engineerCompliance attestations (SOC 2, HIPAA, PCI) are documented so security review does not stall the rollout

   weight 1 · round drawn
   Snowflake✓fullclaimed8/10

   Snowflake's dedicated Regulatory Compliance documentation explicitly lists per-certification pages for SOC 1 Type II, SOC 2 Type II, PCI DSS, and FedRAMP (a HIPAA-relevant standard), directly addressing the security-review documentation need. This is supported by first-party docs with named certifications, giving platform-engineers concrete attestation references. Missing for 10: an explicit named HIPAA compliance page/BAA reference and independent third-party corroboration of audit currency.

   • [claimed-docs] “Docs, "Regulatory compliance": "Snowflake is committed to meeting industry-standard regulatory compliance requirements", with per-certificat…”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   Google Cloud's compliance resource center explicitly documents BigQuery-covered attestations including SOC 1/2/3, HIPAA support, ISO 27001-family certs, and downloadable audit reports, directly satisfying a platform-engineer's need for security-review documentation. Missing for 10: explicit PCI DSS attestation mention (only general 'sector/regional programs' referenced) and no independent third-party corroboration of the compliance claims.

   • [claimed-docs] “Google Cloud compliance resource center lists BigQuery-covered attestations and certifications including ISO 9001:2015, ISO 22301:2019, ISO …”

   proof ↗⚑ flag

Connectors

1. data-engineerFirst-party and partner connectors cover my sources — SaaS apps, databases, and ETL/ELT tools — with documented setup

   weight 2 · round to BigQuery
   Snowflake~partialclaimed4/10

   The pack shows Snowflake integrates with ETL/ELT tooling (dbt Projects on Snowflake, managed dbt runtimes) and general data-loading mechanisms (Snowpipe, COPY INTO, Iceberg tables for external lakes) with documented setup, but it never documents a first-party/partner connector catalog for specific SaaS apps (e.g., Salesforce, HubSpot) or databases (e.g., Postgres, MySQL) — no Partner Connect, native connectors gallery, or marketplace connector docs are cited. Missing for 10: documented SaaS-app connector catalog, database-source connector docs, partner ETL/ELT integration listings beyond dbt.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Apache Iceberg™ tables for Snowflake combine the performance and query semantics of typical Snowflake tables with external cloud storage tha…”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”

   proof ↗⚑ flag

   BigQuery~partialcommunity5/10

   BigQuery's docs show database replication ('replicating data from databases to BigQuery in near real time'), scheduled load jobs, Pub/Sub streaming ingestion, Dataform for ELT transformation workflows, and ODBC/JDBC drivers for tool connectivity — a real but partial connector story. However, there's no evidence of BigQuery Data Transfer Service or a documented catalog of first-party/partner SaaS-app connectors (e.g. Google Ads, Analytics, Salesforce, Fivetran/Stitch-style partner ecosystem), and one community report notes CloudSQL-to-BigQuery ingestion historically required a third-party tool rather than a native connector. Missing for 10: explicit SaaS-app connector documentation, a partner-connector directory/marketplace, and independent confirmation that documented setup for diverse source types (beyond DBs/Pub/Sub) is straightforward.

   • [claimed-docs] “This method enables replicating data from databases to BigQuery in near real time.”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub.”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [community] “Last time I checked, it was still hard to get a Google CloudSQL DB into BigQuery, so it's surprising they did the Sheets integration first; …”

   proof ↗⚑ flag

Loading

1. data-engineerBulk-load CSV, JSON, and Parquet from cloud object storage with a single documented command

   weight 3 · round to BigQuery
   Snowflake~partialcommunity5/10

   Evidence confirms Snowflake's COPY INTO/Snowpipe ingestion path from cloud stages (referenced via stream and Snowpipe docs, plus a community mention of COPY skipping already-loaded files and JSON Lines usage) and separate support for semi-structured JSON data types, but the pack never explicitly documents a single COPY INTO command example covering CSV, JSON, and Parquet together. missing for 10: explicit doc snippet naming CSV/Parquet file format support in COPY INTO, and a concrete single-command example spanning all three formats.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “SQL reference, "Semi-structured data types" (VARIANT/OBJECT/ARRAY) with guides "Introduction to loading semi-structured data", "Querying Sem…”
   • [community] “Regarding combining to a single file for loading: not necessary... Just make them JSON Lines. The COPY command will even skip files it has a…”

   proof ↗⚑ flag

   BigQuery✓fullprobed9/10

   BigQuery's documented `bq load` command and load jobs support single-command bulk loading of CSV, JSON, and Parquet directly from Cloud Storage, with scheduling and batch options documented (bigquery-docs-41, bigquery-docs-12/49/58). This is a well-established, heavily documented core capability. Missing for 10: independent hands-on confirmation specifically of the load command (community evidence covers pricing/perf but not load-command usage) and explicit mention of all three formats in one citation.

   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “you learn how to use `bq`, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query …”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   proof ↗⚑ flag

2. data-engineerA managed service continuously ingests new files or events as they arrive, without me running my own pipeline infrastructure

   weight 2 · round drawn
   Snowflake✓fullcommunity8/10

   Snowpipe is a first-party managed service that automatically loads files from a stage as soon as they arrive, in micro-batches within minutes, without manual COPY scheduling or customer-run pipeline infrastructure (snowflake-docs-6/20/29/34/44/76). Community evidence corroborates continuous file-based loading behavior (COPY skipping already-loaded files) consistent with this pattern (snowflake-comm-4). Missing for 10: explicit documentation of event-driven/streaming ingestion (e.g., Snowpipe Streaming API or Kafka connector) and independent hands-on validation of the 'no pipeline infra' claim beyond vendor docs.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches”
   • [community] “Regarding combining to a single file for loading: not necessary... Just make them JSON Lines. The COPY command will even skip files it has a…”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery provides multiple fully-managed ingestion paths for continuously arriving data: the Storage Write API with exactly-once semantics for streaming writes, a native Pub/Sub-to-BigQuery subscription for high-throughput event streaming, Continuous Queries for real-time analysis of incoming data, and scheduled or near-real-time database replication load jobs, all without the user provisioning or operating pipeline infrastructure. Docs explicitly market BigQuery as having no infrastructure to set up or manage. Missing for 10: independent or hands-on evidence validating continuous streaming ingestion at scale, and more detail on CDC or file-arrival-triggered ingestion beyond Pub/Sub and replication mentions.

   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub.”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”
   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “This method enables replicating data from databases to BigQuery in near real time.”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “there's no infrastructure to set up or manage, letting you focus on finding meaningful insights using GoogleSQL or Python”

   proof ↗⚑ flag

Notebooks

1. analystFirst-party notebooks let me mix SQL and Python against warehouse data, with results and charts inline

   weight 2 · round drawn
   Snowflake✓fullcommunity8/10

   Snowflake Notebooks is a first-party, cell-based Snowsight interface supporting Python, SQL, and Markdown in the same notebook with cell-by-cell execution and result comparison, directly matching the story. Missing for 10: explicit documentation/screenshots of inline chart rendering within notebooks and independent/hands-on user corroboration beyond vendor docs.

   • [claimed-docs] “Write SQL or Python code and quickly compare results with cell-by-cell development and execution.”
   • [claimed-docs] “Snowflake Notebooks is a unified development interface in Snowsight that offers an interactive, cell-based programming environment for Pytho…”
   • [claimed-docs] “you can leverage your Snowflake data to perform exploratory data analysis, develop machine learning models, and perform other data science a…”
   • [community] “Snowflake's preview app called Snowsight provides a way to both query and visualize the data.”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery's notebooks feature explicitly combines SQL queries, Python code, rich text, and inline visualizations, with Colab Enterprise integration enabling end-to-end data science/ML workflows in one interface. This directly matches the analyst story of mixing SQL/Python with inline results and charts. Missing for 10: independent/hands-on corroboration of the notebook experience beyond first-party docs, and detail on how seamlessly SQL and Python cells interoperate in practice.

   • [claimed-docs] “notebooks let you combine SQL queries with Python code, rich text, and visualizations to tell a comprehensive story with your data.”
   • [claimed-docs] “Colab Enterprise notebooks in BigQuery let you perform end-to-end data science and machine learning workflows within a single, integrated in…”
   • [claimed-docs] “End-to-end ML workflows: build, evaluate, and deploy a BigQuery ML model within a single notebook interface.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to BigQuery
   Snowflake~partialprobed6/10

   Snowflake exposes broad programmatic surfaces — the SQL API and REST APIs for resource management (queries, provisioning users/roles, tables), Snowpark APIs, Snowflake CLI for managing apps/workloads, and OpenAPI-compliant specs published on GitHub — indicating strong API/UI parity ambitions for developers and AI agents (docs-65, docs-66, docs-72, docs-73, snowflake-supp-openapi-specs, docs-1). However there is no explicit vendor claim or independent verification of full 1:1 parity between every Snowsight UI feature (e.g., notebooks cell UI, query profile visualizations, Cortex Analyst chat UI) and API equivalents, and a live probe found no discoverable openapi.json at conventional doc paths. Missing for 10: an explicit parity statement or audit confirming every UI action has an API/CLI equivalent, and independent/hands-on confirmation that AI-native workflows can fully replace UI usage.

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “With Snowflake CLI, developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflak…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   BigQuery~partialprobed7/10

   BigQuery exposes a comprehensive, self-describing REST API (datasets/jobs/models/tables/routines) plus the bq CLI and client libraries, and SQL/DML/ML training operations that appear in the UI are all reachable via API or SQL statements — core data and query operations have strong API parity. However, several newer UI-centric features (Gemini-powered conversational analytics, BigQuery Data Canvas, notebook-based workflows) are documented as console experiences without clear evidence of an equivalent programmatic/API path for all their functionality. Missing for 10: explicit documentation that conversational analytics/Data Canvas/notebook features are fully accessible via API rather than console-only, and independent hands-on confirmation of full UI/API parity.

   • [probe] “PROBE runtime (recorded 2026-09-06): the BigQuery v2 REST discovery document downloaded keylessly from bigquery.googleapis.com and parsed cl…”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”
   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “Data Manipulation Language (DML) statements enable you to update, insert, and delete data from your BigQuery tables.”
   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “notebooks let you combine SQL queries with Python code, rich text, and visualizations to tell a comprehensive story with your data.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Snowflake~partialcommunity5/10

   Snowflake supports Apache Iceberg tables backed by open, customer-managed cloud storage, which is a genuine open-format, portable-data path, and it exposes SQL/REST APIs for programmatic data extraction. However, there is no direct documentation in the evidence pack of a comprehensive 'export all your data and leave' workflow (e.g., bulk UNLOAD/COPY INTO to open formats for all tables, migration tooling, or explicit anti-lock-in guidance), and community commentary even frames Snowflake's stickiness/lock-in as a concern rather than confirming easy full data egress. Missing for 10: documented bulk export/unload feature for all data, first-party migration/exit tooling, and independent confirmation that a full data exit is straightforward.

   • [claimed-docs] “Apache Iceberg™ tables for Snowflake combine the performance and query semantics of typical Snowflake tables with external cloud storage tha…”
   • [claimed-docs] “They are ideal for existing data lakes that you cannot, or choose not to, store in Snowflake.”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [community] “I predict we'll see more people choosing Clickhouse over Snowflake in the next 5 years... and give people a better escape hatch if they want…”

   proof ↗⚑ flag

   BigQuery~partialclaimed5/10

   BigQuery documents Iceberg managed tables that store data in customer-owned buckets in the open Apache Iceberg format for interoperability with third-party/open-source engines, and states general support for open table formats like Iceberg, Delta, and Hudi, addressing data portability/lock-in concerns. However, evidence does not show a dedicated bulk-export mechanism (e.g. bq extract to CSV/Avro/Parquet/JSON) for standard native BigQuery tables, nor confirmation that ALL data (not just tables opted into Iceberg format) can be freely exported without proprietary lock-in. Missing for 10: documented export/extract tooling for native tables in open formats, evidence of full-dataset export workflows, and independent confirmation that migrating away is friction-free.

   • [claimed-docs] “Iceberg managed tables offer the same fully managed experience as standard BigQuery tables, but store data in customer-owned storage buckets…”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines on…”
   • [claimed-docs] “BigQuery provides a uniform way to work with both structured and unstructured data and supports open table formats like Apache Iceberg, Delt…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Snowflake—none0/10

   The evidence pack includes compliance certifications (SOC 2, ISO, FedRAMP, PCI DSS) but contains no mention of region selection, data residency controls, or ability to choose a storage location/cloud region for an account or database. No documentation cited addresses this specific capability.

   ⚑ flag

   BigQuery—none0/10

   The evidence pack contains no documentation or mention of choosing a dataset/table region, multi-region options, or data residency controls for BigQuery; only general compliance certifications and unrelated feature descriptions are provided. Missing for 10: explicit docs on selecting dataset location/region, data residency guarantees, or region-locking configuration.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Snowflake—none0/10

   The axis applies since Snowflake offers AI/Cortex features built on third-party LLMs, making data-use-for-training a fair privacy concern, but no evidence pack item documents an opt-out control, data-processing agreement, or explicit statement that customer data is excluded from model training. Compliance certifications and RBAC/access-history items are about general security/governance, not AI-training data use.

   ⚑ flag

   BigQuery—none0/10

   The evidence pack covers BigQuery's features (SQL, Gemini in BigQuery, pricing, sharing, compliance certifications) but contains no documentation of a specific data-usage policy or customer control for opting out of having data used to train Google's AI models, despite BigQuery now integrating Gemini AI features. Missing for 10: explicit AI-training data-usage policy, opt-out/opt-in controls, and any documentation addressing whether customer data feeds model training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Snowflake~partialclaimed5/10

   Snowflake's Time Travel docs show a defined retention window for querying/restoring changed or deleted data, and RBAC plus compliance certifications provide governance context, giving an AI-native user some levers over data lifecycle and access. Missing for 10: explicit documentation of configuring the retention period (e.g., DATA_RETENTION_TIME_IN_DAYS parameter), explicit purge/permanent-delete commands, and any GDPR/right-to-erasure specific deletion guarantees.

   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted.”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted. You can restore individual objects, such as tables, or restore…”
   • [claimed-docs] “Snowflake Time Travel enables accessing historical data (that is, data that has been changed or deleted) at any point within a defined perio…”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Docs, "Regulatory compliance": "Snowflake is committed to meeting industry-standard regulatory compliance requirements", with per-certificat…”

   proof ↗⚑ flag

   BigQuery~partialclaimed5/10

   BigQuery's DML supports DELETE operations on tables (bigquery-docs-2) and Iceberg managed tables reference 'time travel for historical data access' (bigquery-docs-44), giving users mechanisms to remove or manage historical data, and IAM/access-control docs show governance controls exist (bigquery-docs-31). However, there is no direct documentation of retention policy configuration (e.g., table/partition expiration settings) or a dedicated data-deletion/GDPR compliance workflow in the evidence pack. Missing for 10: explicit table/dataset expiration policy docs, a dedicated data retention & deletion API/console feature, and independent confirmation that deletion requests are honored end-to-end.

   • [claimed-docs] “Data Manipulation Language (DML) statements enable you to update, insert, and delete data from your BigQuery tables.”
   • [claimed-docs] “Time travel for historical data access in BigQuery.”
   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Snowflake—none0/10

   No evidence pack item mentions telemetry, usage tracking, or an opt-out mechanism for Snowflake's own product telemetry; only compliance certifications and access-history/audit features are documented, which don't address user-facing telemetry opt-out. This axis is applicable to any AI-native SaaS product, so absence of evidence yields 'none'. Missing for 10: any documentation of a telemetry/usage-data collection policy or an opt-out/opt-in control for such tracking.

   ⚑ flag

   BigQuery—none0/10

   The evidence pack contains no mention of BigQuery collecting telemetry/usage data from client tools (bq CLI, client libraries, notebooks) nor any documented opt-out mechanism, despite this being a plausible axis for a cloud data platform with CLI/SDK tooling. missing for 10: any documentation of telemetry collection practices, an opt-out flag/setting (e.g., in bq CLI or client SDKs), or privacy-posture statements addressing usage tracking.

   ⚑ flag

Semantics

1. analystDefine a governed semantic model — metrics, dimensions, and joins declared once — that queries and AI tools answer against consistently

   weight 2 · round to Snowflake
   Snowflake✓fullclaimed7/10

   Snowflake's Semantic Views let analysts declare business metrics, entities, and relationships once as schema-level objects, and Cortex Analyst answers natural-language questions against this same semantic layer without writing SQL, while Cortex Agents/MCP expose it to AI tools — directly matching the story of a governed semantic model queried consistently by both SQL and AI. missing for 10: no independent/community corroboration of Semantic Views in practice, and no detail on how BI/SQL query tools (beyond Cortex Analyst) consistently reuse the same semantic definitions.

   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object. You can define busines…”
   • [claimed-docs] “You can define business metrics and model business entities and their relationships.”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View ... define business metrics and model business entities…”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object.”
   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   BigQuery—none0/10

   The evidence pack shows BigQuery's SQL engine, Dataform (ELT transformation), notebooks, and Gemini natural-language querying, but no dedicated semantic-layer feature where metrics, dimensions, and joins are declared once and consistently reused across queries and AI tools (e.g., no LookML/metrics-layer equivalent is documented here). Dataform manages transformation pipelines, not a governed semantic/metrics model, so the specific capability described in the story is unevidenced.

   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “Query statements... are the primary method to analyze data in BigQuery.”

   proof ↗⚑ flag

Sharing

1. analystA marketplace of third-party datasets lets me enrich my own data directly inside the platform

   weight 1 · round to BigQuery
   Snowflake—none0/10

   The evidence pack only documents Secure Data Sharing (share selected objects between Snowflake accounts) but contains no mention of a marketplace, data exchange, or third-party dataset listings that an analyst could browse and directly enrich their own data with — the specific marketplace capability described in the story is absent from the pack.

   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts.”
   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts. ... no actual data is copie…”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery sharing (formerly Analytics Hub) is explicitly documented as a data exchange platform for discovering, sharing and accessing third-party/Google curated datasets and combining them with internal data, directly inside the platform. Multiple docs confirm this cross-org discovery and combination workflow. Missing for 10: independent hands-on evidence/user reports specifically validating the marketplace discovery/enrichment workflow (community evidence only covers other BigQuery aspects like pricing/performance, not the marketplace).

   • [claimed-docs] “La condivisione di BigQuery (precedentemente Analytics Hub) è una piattaforma di scambio di dati che consente di condividere, scoprire e acc…”
   • [claimed-docs] “Puoi utilizzare BigQuery sharing per scoprire set di dati curati di terze parti e di Google e combinarli con i tuoi dati interni”
   • [claimed-docs] “BigQuery sharing (formerly Analytics Hub) is a data exchange platform that lets you securely share, discover, and access data across organiz…”
   • [claimed-docs] “La condivisione di BigQuery... è una piattaforma di scambio di dati che consente di condividere, scoprire e accedere in modo sicuro ai dati …”

   proof ↗⚑ flag

2. data-engineerShare live datasets with another account or organization without copying data or building an export pipeline

   weight 2 · round drawn
   Snowflake✓fullclaimed9/10

   Snowflake's Secure Data Sharing directly delivers this story: it lets accounts share selected database objects with other Snowflake accounts, with docs explicitly stating no actual data is copied or transferred between accounts, eliminating the need for export pipelines. This is a first-party, well-documented core Snowflake feature (also referenced as part of Standard plan capabilities). Missing for 10: independent/hands-on third-party confirmation of cross-organization sharing experience beyond vendor docs.

   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts.”
   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts. ... no actual data is copie…”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”

   proof ↗⚑ flag

   BigQuery✓fullclaimed9/10

   BigQuery sharing (formerly Analytics Hub) is explicitly documented as a data exchange platform enabling secure sharing, discovery, and access to data across organizational boundaries without replicating data—exactly matching the story of sharing live datasets with another account/org without copying or building an export pipeline. Missing for 10: independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “La condivisione di BigQuery (precedentemente Analytics Hub) è una piattaforma di scambio di dati che consente di condividere, scoprire e acc…”
   • [claimed-docs] “La condivisione di BigQuery... è una piattaforma di scambio di dati che consente di condividere, scoprire e accedere in modo sicuro ai dati …”
   • [claimed-docs] “Puoi utilizzare BigQuery sharing per scoprire set di dati curati di terze parti e di Google e combinarli con i tuoi dati interni”
   • [claimed-docs] “BigQuery sharing (formerly Analytics Hub) is a data exchange platform that lets you securely share, discover, and access data across organiz…”

   proof ↗⚑ flag

Lakehouse

1. data-engineerQuery open table formats and files in object storage — Iceberg, Delta, Parquet — without first loading them into proprietary storage

   weight 2 · round drawn
   Snowflake✓fullclaimed8/10

   Snowflake supports Apache Iceberg tables directly on customer-managed external cloud storage, explicitly positioned for 'existing data lakes that you cannot, or choose not to, store in Snowflake,' and Snowpipe/COPY plus external stages allow querying files in object storage without loading them into proprietary storage. Missing for 10: explicit docs on Delta Lake table querying and independent hands-on benchmarks confirming performance parity for external Iceberg/Delta queries.

   • [claimed-docs] “Apache Iceberg™ tables for Snowflake combine the performance and query semantics of typical Snowflake tables with external cloud storage tha…”
   • [claimed-docs] “They are ideal for existing data lakes that you cannot, or choose not to, store in Snowflake.”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery explicitly supports querying open table formats (Iceberg, Delta, Hudi) and files in object storage without ingesting them into proprietary storage — Iceberg managed tables store data in customer-owned buckets with schema evolution and time travel, and BigQuery natively supports open table formats per its intro docs. Missing for 10: independent hands-on validation of querying Delta/Parquet files directly (only Iceberg is detailed with specifics), and no community corroboration of external-table performance/limitations for these formats.

   • [claimed-docs] “BigQuery provides a uniform way to work with both structured and unstructured data and supports open table formats like Apache Iceberg, Delt…”
   • [claimed-docs] “Iceberg managed tables offer the same fully managed experience as standard BigQuery tables, but store data in customer-owned storage buckets…”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines on…”
   • [claimed-docs] “_Schema evolution_, which lets you add, drop, and rename columns to suit your needs.”
   • [claimed-docs] “Time travel for historical data access in BigQuery.”

   proof ↗⚑ flag

Performance

1. data-engineerInspect query profiles and execution plans to find why a query is slow or expensive

   weight 2 · round to BigQuery
   Snowflake✓fullcommunity8/10

   Snowsight's Query History page lets data engineers monitor executed queries and drill into a detailed query profile that explores each step of execution, directly supporting root-cause analysis of slow/expensive queries; this is corroborated by community mention of Snowsight's query/visualize UI. missing for 10: no independent hands-on account of using query profile specifically to diagnose a slow query, and no detail on cost-per-query attribution tooling (one community comment even notes lack of query-level cost attribution).

   • [claimed-docs] “With the Query History page in Snowsight, you can do the following: Monitor individual or grouped queries that are executed by users in your…”
   • [claimed-docs] “The Query History page lets you explore queries executed in your Snowflake account over the last 14 days.”
   • [claimed-docs] “Explore each step of an executed query in the query profile.”
   • [claimed-docs] “Monitor individual or grouped queries that are executed by users in your account.”
   • [community] “Snowflake's preview app called Snowsight provides a way to both query and visualize the data.”
   • [community] “The problem with Snowflake is particularly worse due to its lack of query level attribution of costs and no in-built features for monitoring…”

   proof ↗⚑ flag

   BigQuery✓fullcommunity9/10

   BigQuery documents dedicated query plan/execution diagnostics via EXPLAIN-like output and timing information, letting engineers inspect stages, slot usage, and bottlenecks; the pricing model also exposes bytes-scanned/dry-run cost estimation used to diagnose expensive queries. Missing for 10: independent hands-on walkthroughs of using the query plan UI to debug a real slow query (only docs mention the feature, no community corroboration of using execution plans specifically).

   • [claimed-docs] “BigQuery includes diagnostic query plan and timing information. This is similar to the information provided by statements such as EXPLAIN in…”
   • [claimed-docs] “BigQuery includes diagnostic query plan and timing information. This is similar to the information provided by statements such as `EXPLAIN` …”
   • [community] “BigQuery provides a dry run option to estimate bytes/costs before running a query, and shows bytes-to-be-scanned in small text before you hi…”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”
   • [claimed-docs] “You can also reserve compute capacity ahead of time in the form of slots, which represent virtual CPUs.”

   proof ↗⚑ flag

Recovery

1. data-engineerTime-travel — query data as of a past point and restore dropped or corrupted tables from history

   weight 2 · round to Snowflake
   Snowflake✓fullclaimed9/10

   Snowflake's documented Time Travel feature explicitly supports querying data as of a past point and restoring accidentally/intentionally deleted objects (tables, schemas, databases) within a retention window, directly matching the story; Clone/UNDROP mechanics and object cloning (inheriting privileges) further support restoration workflows. Missing for 10: no independent/hands-on corroboration of restore success or retention-period limits from community evidence.

   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted.”
   • [claimed-docs] “Query data in the past that has since been updated or deleted.”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted. You can restore individual objects, such as tables, or restore…”
   • [claimed-docs] “Snowflake Time Travel enables accessing historical data (that is, data that has been changed or deleted) at any point within a defined perio…”
   • [claimed-docs] “the clone inherits all granted privileges on the clones of all child objects contained in the source object”
   • [claimed-docs] “If the source object is a database or schema, the clone inherits all granted privileges on the clones of all child objects contained in the …”

   proof ↗⚑ flag

   BigQuery~partialclaimed3/10

   Only one brief doc mention confirms BigQuery supports time travel for historical data access, but the evidence pack lacks detail on the retention window, querying historical snapshots via SQL syntax, or the fail-safe/restore-dropped-table mechanism, and has no independent/hands-on corroboration. missing for 10: documentation on the time-travel query syntax (FOR SYSTEM_TIME AS OF), the default/configurable retention window, explicit restore-dropped-table (fail-safe) workflow, and any community validation of these mechanisms.

   • [claimed-docs] “Time travel for historical data access in BigQuery.”

   proof ↗⚑ flag

Sql

1. analystI get a full analytical SQL surface — window functions, CTEs, semi-structured JSON, arrays, and rich date/time types — without bolt-on extensions

   weight 3 · round to BigQuery
   Snowflake~partialcommunity7/10

   Docs confirm window functions, semi-structured VARIANT/OBJECT/ARRAY types, and Time Travel/date handling are native SQL features, and community evidence corroborates JSON handling via COPY/JSON Lines. However, one community report notes a gap versus generate_series-style sequence generation, and CTE support and rich date/time type breadth aren't directly evidenced in the pack. missing for 10: explicit CTE documentation, comprehensive date/time type reference, independent corroboration beyond the noted generate_series gap.

   • [claimed-docs] “SQL reference, "Window functions": "Window functions are analytic functions that you can use for various calculations such as running totals…”
   • [claimed-docs] “SQL reference, "Semi-structured data types" (VARIANT/OBJECT/ARRAY) with guides "Introduction to loading semi-structured data", "Querying Sem…”
   • [community] “Snowflake doesn't have a generate_series function equivalent. The closest thing it has is a generator function which only accepts constants.”
   • [community] “Regarding combining to a single file for loading: not necessary... Just make them JSON Lines. The COPY command will even skip files it has a…”
   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”

   proof ↗⚑ flag

   BigQuery✓fullcommunity8/10

   BigQuery's GoogleSQL is documented as ANSI-compliant with support for DML, query statements, and a full analytical surface including window functions, CTEs, arrays/structs, JSON handling, and date/time types (implied by GoogleSQL SQL reference and confirmed by community praise of pipe syntax and table-valued functions). Independent hands-on testimony (bigquery-comm-15, bigquery-comm-16) confirms real analyst usage of advanced SQL constructs without extensions. Missing for 10: explicit doc citations enumerating window functions, JSON/array functions, and DATETIME/TIMESTAMP types individually rather than inferred from general SQL intro docs.

   • [claimed-docs] “Query statements... are the primary method to analyze data in BigQuery.”
   • [claimed-docs] “GoogleSQL is an ANSI-compliant Structured Query Language (SQL) that includes the following types of supported statements”
   • [claimed-docs] “Data Manipulation Language (DML) statements enable you to update, insert, and delete data from your BigQuery tables.”
   • [community] “Review after a week of using BigQuery's new SQL pipe syntax: much more productive for data exploration/cleaning, unifies WHERE/HAVING/QUALIF…”
   • [community] “BigQuery has table-valued functions already, which can be used with pipes with a CALL clause.”

   proof ↗⚑ flag

Streaming

1. data-engineerRun continuous or incremental transformations — streams, tasks, declarative pipelines, or continuous queries — inside the platform

   weight 1 · round drawn
   Snowflake✓fullclaimed8/10

   Snowflake documents Streams for CDC-based incremental change capture (doc-7/21/38/54), Dynamic Tables (GA, doc-15) for declarative continuous transformation pipelines, and Snowpipe for continuous/micro-batch ingestion (doc-6/20/29/34/44/76) — directly matching the story's streams/declarative-pipeline/continuous-processing capabilities inside the platform. Missing for 10: explicit documentation of the Tasks object (scheduling/orchestration companion to Streams), Snowpipe Streaming (true low-latency continuous ingestion) specifics, and independent/hands-on validation of these pipelines at production scale.

   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “CREATE OR ALTER DYNAMIC TABLE (General availability)”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts, updates, and deletes”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables... so that actions can be taken using the changed data”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery provides continuous queries (SQL statements running continuously to analyze streaming data in real time) as a first-class feature, plus Dataform for declarative, version-controlled, scheduled transformation pipelines with dependency graphs, and streaming ingestion via Storage Write API/Pub/Sub subscriptions for near-real-time pipelines. Together these cover streams, tasks/scheduled pipelines, declarative pipelines, and continuous queries as described in the story. Missing for 10: independent/hands-on validation of continuous queries at scale and clearer documentation of latency/cost tradeoffs in production use.

   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “View a visualization of the dependency tree of your workflow.”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub.”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “This method enables replicating data from databases to BigQuery in near real time.”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “The Storage Write API (gRPC) has lower pricing and more robust features, including exactly-once delivery semantics.”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”

   proof ↗⚑ flag

2. data-engineerStreaming writes land queryable within seconds through a documented streaming ingestion API

   weight 2 · round to BigQuery
   Snowflake~partialclaimed4/10

   Snowflake documents Snowpipe as a streaming/micro-batch ingestion API, but the documentation explicitly states data becomes available 'within minutes,' not seconds, directly at odds with the story's 'queryable within seconds' requirement. There is no evidence pack mention of the lower-latency Snowpipe Streaming API or REST-based streaming ingestion that could close this gap. Missing for 10: documented sub-second/seconds-level ingestion latency, evidence of a dedicated low-latency streaming ingestion API (e.g., Snowpipe Streaming), and independent/hands-on confirmation of near-real-time query availability.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches”

   proof ↗⚑ flag

   BigQuery✓fullclaimed8/10

   BigQuery's Storage Write API (gRPC) is documented as a real-time streaming ingestion API with exactly-once delivery semantics, and continuous queries/Pub/Sub subscriptions confirm data becomes queryable in near real time. missing for 10: no independent/hands-on benchmark confirming actual seconds-level latency from write to queryability, and no explicit SLA/numeric latency figure in docs.

   • [claimed-docs] “The Storage Write API (gRPC) has lower pricing and more robust features, including exactly-once delivery semantics.”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”

   proof ↗⚑ flag