Google Cloud Data Updates Bring AI Agents Closer to Production

Oct 29, 2026 572 views

Google Cloud’s October data push puts agents closer to production

Google Cloud’s October updates point to a broader shift: data products are being reshaped to give AI agents trusted context, access to operational systems, and ways to run across different environments. That’s more significant than a stack of feature announcements. The harder question is whether these pieces make agents dependable enough for real work; several of the performance claims are based on internal benchmarks, so they deserve that caveat.

October 26–30

  • Knowledge Catalog adds self-learning enrichment and Knowledge Studio preview. Its enrichment agent learns from user and agent interactions, along with playbooks, code repositories, and business documents, to identify missing or stale context. Teams can package the resulting context into reusable sets. The new Knowledge Studio gives context engineers and data stewards a conversational way to explore their data estate, inspect a visual context graph, and review changes before users or agents see them. Google says internal benchmarks found that grounding agents in Knowledge Catalog made them nearly four times more accurate, with up to 33% lower latency and up to 75% fewer tokens. Those are striking figures, though the announcement doesn’t explain the benchmark conditions. Read the launch blog.
  • Knowledge Catalog reaches semantic models teams already rely on (GA). It can now ingest semantic models and metric definitions from Looker LookML, BigQuery Graph, dbt MetricFlow, Snowflake Semantic Views, Databricks Metric Views, and SAP Core Schema Notation. The catalog links those definitions to lineage, data quality, and access controls in one context graph. Gemini Enterprise, BigQuery conversational analytics, and custom agents can retrieve a metric’s trusted formula, verified join path, and backing table in a single context call, without moving data or rewriting business logic. For teams trying to keep agent answers aligned with established business definitions, that integration is the point. Read the launch blog.

October 19–23

  • BigQuery adds column aliases in GoogleSQL and makes cross-region table copy generally available. Column aliases can now be used in SELECT and WHERE clauses through a GA opt-in, reducing nested subqueries and easing migrations from Snowflake and Teradata. Cross-region table copying is also GA, aimed at regional replication and disaster recovery. Review the BigQuery release notes.
  • BigQuery conversational analytics adds Canadian regions and CSV/PDF export. The service is available in Montréal (northamerica-northeast1) and Toronto (northamerica-northeast2), addressing Canadian data residency requirements. Agent responses—including text, tables, charts, and citations—can now be exported directly to CSV or PDF (GA). Learn more about conversational analytics in BigQuery.
  • AlloyDB Omni 18.4.0 is GA, with query diagnostics and external key management. The release brings PostgreSQL 18.4 to self-hosted and multi-cloud environments. Its google_insights_v2 extension provides granular query execution and wait-event diagnostics. For Transparent Data Encryption (TDE), it adds Thales CipherTrust Manager support alongside HashiCorp Vault. Explore the AlloyDB Omni release notes.
  • Cloud SQL for PostgreSQL adds managed connection pooling and changes its private IP default. Existing Private Service Connect (PSC) instances can enable built-in connection pooling to support high-concurrency workloads. PSC is now the default private IP option for new Cloud SQL instances in new projects, simplifying cross-project networking. Review Cloud SQL updates.
  • Unico says its Google Cloud data architecture has helped prevent more than $5 billion in fraud. The digital identity platform moved from Databricks Spark/Scala clusters to BigQuery and Spanner. By bringing real-time transaction streams together with petabyte-scale analytics, Unico says it can perform low-latency identity verification and has prevented over $5 billion in fraud. Read the Unico case study.
  • A new guide shows developers how to start building Looker Data Apps. After the feature’s preview debut, the Google Developer Community published a walkthrough with practical patterns for creating prompt-driven applications inside Looker. Read the guide on the Google Developer Community.

October 12–16

  • Looker Data Apps enter preview, turning reports into interactive applications. Developers can generate these web apps with natural-language prompts, the Antigravity CLI, or Claude Code, then host them inside Looker. Users can test scenarios, change parameters, and trigger workflows in downstream platforms. The apps inherit LookML semantic modeling, row-level security, and access controls, and incur no runtime LLM token costs. The promise is to move business reporting toward operational action; how far teams take that will depend on the workflows they connect. Read the announcement blog.
  • The Data Agent Kit gets an end-to-end data science walkthrough. Following the kit’s general availability, a new guide demonstrates how data teams can build, test, and schedule machine learning pipelines from their preferred code editors. Data Agent Kit; Explore the walkthrough and codelab.
  • LookML dashboard agents can now be managed as code. Teams can keep agent parameters, configurations, and prompt instructions alongside dashboard files. That brings Git version control, peer review, branching, and automated CI/CD validation to conversational BI, so agent changes can be checked before reaching production users. Read the technical guide on the Google Developer Community.
  • AlloyDB adds native hybrid search with Reciprocal Rank Fusion. AlloyDB for PostgreSQL can combine vector similarity with keyword BM25 retrieval in one database engine. Reciprocal Rank Fusion (RRF) merges lexical scores and semantic embeddings into a ranked result without requiring a complex SQL query. The aim is to avoid operating and synchronizing a separate search engine alongside an operational database for retrieval-augmented generation (RAG) and search applications. Explore hybrid search in AlloyDB.

October 5–9

Analytics and infrastructure updates

Three BigQuery additions target different parts of the analytics workflow. Six augmented analytics table-valued functions automate metric diagnostics, trend analysis and pattern discovery where the data is stored. They can also serve as skills for AI agents. TabFM brings tabular foundation model capabilities to predictive analytics, while identity columns generate sequential surrogate keys automatically. The latter is a smaller change, but it addresses a common source of friction in warehouse pipelines.

For larger AI workloads, Dataflow adds Pause/Resume controls and support for NVIDIA RTX PRO 6000 Blackwell GPUs, aimed at high-throughput streaming and batch pipelines. Spark teams can also use flexible VMs to reduce compute stockouts and improve availability.

Google reports gains across its data cloud customer base, though the examples span different products and workloads. Yahoo says flexible VMs in Managed Service for Apache Spark cut provisioning failures by 85%; PayPal moved mission-critical analytics workloads to the service to scale while reducing operational overhead. Surescripts moved 30.5 billion annual healthcare transactions to AlloyDB and reports 99.998% uptime. Airwallex runs more than 5,000 databases on Cloud SQL with 99.99% availability and a team of four DBAs. Lucius AI operates a global platform covering 210,000 tenders on AlloyDB and MCP, with ScaNN vector search reported to be 47 times faster.

More on Yahoo, PayPal, Surescripts, Airwallex and Lucius AI.

September 7–10

Pub/Sub can now run AI inference on incoming event streams using models hosted on Gemini Enterprise Agent Platform. The generally available AI Inference SMTs append each model prediction to its event, making it available to downstream systems such as BigQuery or Bigtable. That could simplify anomaly detection workflows, although the announcement doesn’t specify which models or inference patterns are supported.

Managed Service for Apache Kafka’s PostgreSQL source connector is also generally available. It captures database changes and sends them to Kafka with low latency. Supported sources include Cloud SQL for PostgreSQL, AlloyDB and self-managed PostgreSQL. It joins managed connectors for MirrorMaker 2.0, BigQuery, Cloud Storage and Pub/Sub. Questions or feedback can go to kafka-hotline@google.com.

Dataflow pause-on-failure is now generally available for batch jobs. It preserves a job’s state before failure, giving teams time to resolve external issues and resume without discarding completed work. The feature is intended to help manage costs and reliability during temporary outages or capacity constraints.

BigQuery has renamed the insertAll streaming API as the BigQuery Storage Write API (REST). Existing users need to make no code changes: the endpoint remains fully backward compatible. The stateless JSON-over-HTTPS API offers a lighter option than gRPC libraries for serverless web apps, IoT telemetry and AI logging. For high-throughput, continuous pipelines, Google still recommends the Storage Write API (gRPC).

August 31–September 4

BigQuery continuous queries now support stateful operations in Preview. Teams can use joins, aggregations and window functions in streaming queries—for example, to calculate a rolling 30-minute average and send richer real-time signals to applications or AI agents. The documentation has details; feedback is welcome at bq-continuous-queries-feedback@google.com.

Kafka users can now generate mock data for a cluster with a generally available synthetic data tool. It takes three clicks and can start streaming data in less than two minutes, without modifying a client application or setting up a virtual machine. For a quick cluster check or feature trial, that’s a useful shortcut. See the quickstart.

Dataflow pipeline updates are generally available with more flexible migration options. Teams can stop and replace a pipeline, or use a parallel pipeline to speed the transition from the old version to the new one and reduce disruption. A timeout on drains can also limit costs if processing gets stuck. See the upgrade guide and the instructions for updating a pipeline.

July 6–10

Google-managed Apache Iceberg tables for Lakehouse are in Preview and available in the console. The pitch is a shared storage layer that supports native reads and writes across multiple engines, avoiding duplicate pipelines and synchronization work between BigQuery and open-source tools. Teams can run concurrent DML and DDL operations across analytics tools, while automated management handles compaction and partition tuning. Whether that reduces operational work in practice will depend on how well the managed tables fit each team’s existing engines and workflows. Details are in the Lakehouse tables documentation.

June events

The “Beyond the Query: Powering AI Agents with Bigtable, Firestore & Memorystore” series covers updates to Google Cloud’s NoSQL database portfolio. It’s aimed at both newcomers and existing users interested in capabilities announced at Next ’26. Register for the series.

Google Cloud Labs is also running technical Cloud Engineer’s AI Toolkit workshops for platform engineers, SREs and cloud infrastructure teams working to take AI prototypes into production. The sessions cover data-driven work with BigQuery, AlloyDB, Gemini and other tools; more locations are planned. Toronto’s Data Cloud workshop is June 25, with registration here. Chicago’s Data Cloud workshop is June 30; register here.

Google Cloud’s data strategy is becoming an agent strategy

The clearest thread across these announcements is Google’s push to put AI agents closer to the data tools companies already use. The pitch is broader than adding chat to analytics: Google is connecting agents to databases, orchestration systems, and business intelligence products. That could reduce the work between asking a question and acting on an answer. Whether it does so reliably will depend on how well these systems handle real workflows and permissions. Managed Service for Apache Airflow added several pieces aimed at that shift: Airflow 3.1 reached general availability, alongside AI assisted troubleshooting, a managed MCP Server for custom agent integrations, and YAML based orchestration pipelines. [The announcement](https://cloud.google.com/blog/products/data-analytics/managed-apache-airflow-scaling-data-and-ai-workloads) describes the full set of changes. Google also extended agent access to its databases. Managed remote MCP support now covers AlloyDB, Spanner, Cloud SQL, Bigtable, and Firestore, giving AI models a route to database tools used in customer environments. Separately, Google outlined how to [build a BigQuery conversational agent with the Conversational Analytics API](https://cloud.google.com/blog/products/data-analytics/build-data-agents-with-conversational-analytics-api). These agents can interpret natural language, query BigQuery data, and return answers as text, tables, or charts. The practical question is how much context and control customers can provide when agents operate against production data. BigQuery’s own assistant is also changing: [Gemini in BigQuery Studio](https://cloud.google.com/blog/products/data-analytics/gemini-supercharges-the-bigquery-studio-assistant) is being framed as a context aware analytics partner, moving beyond code assistance. And a [Google built ODBC driver for BigQuery](https://docs.cloud.google.com/bigquery/docs/odbc-for-bigquery) is now in preview. It’s open source and designed to give applications a direct, high performance connection to BigQuery. That’s a more conventional infrastructure update, but it matters if teams want their existing applications to reach the same data platform.

Analytics products are opening up

Google is widening the ways people can work with data in Looker and Data Studio. Data Studio is being reintroduced with a larger role: alongside visualizations and reports, it is intended to host BigQuery conversational agents and data apps built in Colab notebooks. [Google’s announcement](https://cloud.google.com/blog/products/data-analytics/looker-studio-is-data-studio) sets out that direction. Looker is gaining [Conversational Analytics for embedded environments](https://cloud.google.com/blog/products/business-intelligence/looker-embedded-adds-conversational-analytics), which lets developers add Gemini powered natural language features to their own data applications. [Self service Explores](https://cloud.google.com/blog/products/business-intelligence/looker-self-service-explores) let users bring their own data into Looker’s semantic layer for ad hoc analysis within a governed environment. The promise is easier access without giving up shared definitions of the data. That balance will determine whether these features help more people answer questions or simply create another interface to manage. Google is also making room for different kinds of analysis. [BigQuery Graph is in preview](https://cloud.google.com/blog/products/data-analytics/introducing-bigquery-graph), offering a scalable way to model, analyze, and visualize large networks of relationships. And for databases that need more read capacity, [Cloud SQL autoscaling read pools](https://cloud.google.com/blog/products/databases/cloudsql-read-pools-support-autoscaling) let teams serve multiple replicas through one read endpoint and adjust capacity as application demand changes.

Promotional offers and customer examples

For teams evaluating Bigtable, Google offers a [10 day free trial](https://cloud.google.com/bigtable) with a one node SSD cluster and up to 500 GB of storage. No credit card is required to start. The trial is positioned for workloads that need low latency, high throughput, and predictable access. New Google Cloud customers can also receive [$300 in free credits](https://docs.cloud.google.com/sql/docs/mysql/create-free-trial-instance). Google points to Telenor, Pet Circle, Fluent Commerce, Lighthouse Intelligence, Wego, and ROLLER as customers using Conversational Analytics and Looker, with Looker’s semantic layer grounding their data insights and actions. The [customer examples](https://cloud.google.com/customers/telenor-looker), [Pet Circle](https://cloud.google.com/customers/petcircle-looker), [Fluent Commerce](https://cloud.google.com/customers/fluent-commerce), [Lighthouse Intelligence](https://cloud.google.com/customers/lighthouse), [Wego](https://cloud.google.com/customers/wego), and [ROLLER](https://cloud.google.com/customers/roller) show where Google says the approach is being applied. They’re useful evidence of adoption, though the announcements don’t quantify the results. Taken together, these releases show Google trying to make its data stack a working environment for AI agents, not just a place to store and report on data. That direction is significant. But the announcements leave open the hardest questions: how dependable the agents are, what guardrails govern database access, and whether the added conversational layers make analysis faster in day to day use.
Source: The Google Cloud Data Analytics, BI, and Database teams · cloud.google.com

Comments

Sign in to comment.
No comments yet. Be the first to comment.

Related Articles

What’s new with Google Data Cloud