Releasesby GlyphAlloyDB real-time BigQuery access adds limit pushdown and runtime projects
The preview feature pushes some LIMIT and OFFSET clauses down to BigQuery to cut network transfer, and optional runtime projects let queries run and bill compute separately from the owning project.
Also shipped Sep 2, 2026Google Cloud in September 2026 →
Openflow Connector for Jira Cloud: Core flow (General availability)
The Atlassian Jira Cloud (Core) flow is now generally available. The flow ingests Jira Cloud issues, projects, users, and related data into dedicated Snowflake tables with explicit schemas. It supports optional deletion tracking and parallel ingestion across projects. The Atlassian Jira Cloud (Agile) flow remains in Public Preview .
Git Folder Serverless is in Beta
You can now use Git Folder Serverless to share serverless compute and a pyproject.toml -managed environment across notebooks and files in a Git folder. See Git Folder Serverless .
[In development] Private Preview: Reader Endpoint for Azure Database for MySQL
We’re happy to announce the public preview of reader endpoint support to simplify connection management when using multiple replicas in Azure Database for MySQL - Flexible Server. A reader endpoint enables automatic load balancing of read-only connection
Fabric Data Agents in Microsoft Copilot Studio (Generally Available)
Organizations can now bring governed business data from Microsoft Fabric into Copilot Studio agents, enabling agents to answer questions, generate insights, and support business processes using trusted enterprise data. Fabric data agents make it easier to ground experiences in the data your organization already relies on.
General availability: Full-text search and the Documents API
Full-text search is now generally available on API version 2026-07, built on the new Documents API. Create schema-based document indexes that combine full-text (BM25), dense-vector, and sparse-vector ranking fields in a single index. Query them with BM25 token matching, Lucene query syntax, or vector similarity, narrowed by metadata and text-match filters.
Enterprise-managed settings support any default model
You can now set your preferred GitHub Copilot model as the default for new conversations through enterprise-managed settings. This lets you choose the default model that best fits your workflows. You can also customize the default by enterprise team, assigning a different default model based on team membership.
More from AlloyDBEvery AlloyDB release →
AlloyDB audit log pipeline status available in Cloud Monitoring
AlloyDB for PostgreSQL instances and nodes now expose the status, throughput and backlog of the audit logging pipeline in Cloud Monitoring.
MCP Toolbox for Databases adds AlloyDB observability and query insights
The Model Context Protocol Toolbox for Databases can now access AlloyDB observability features and advanced query insights directly from an IDE.
You can now use the AlloyDB Columnar Engine as a read-optimized, in-memory cache for HNSW vector indexes
You can now use the AlloyDB Columnar Engine as a read-optimized, in-memory cache for HNSW vector indexes. This feature is generally available ( GA ). It accelerates vector search performance and increases queries per second (QPS) for vector workloads. For more information, see Accelerate queries with the Columnar Engine .
AlloyDB can sync BigQuery tables in preview
BigQuery tables can be synced into AlloyDB once or on a periodic schedule, giving operational analytics low-latency transactional access to data lake data.
AlloyDB integration with BigQuery enters preview
AlloyDB can connect operational and analytical data through real-time lakehouse federation to BigQuery, periodic data synchronization and one-time table syncs, all in preview.
AlloyDB now supports Best Matching 25 (BM25) indexes for full-text search in Preview
AlloyDB now supports Best Matching 25 (BM25) indexes for full-text search in Preview . You can use the pg_textsearch extension to create BM25 indexes and optimize probabilistic ranking of full-text search. This feature is supported on AlloyDB instances running PostgreSQL 17 or 18. For more information, see Create and manage a BM25 index .
Note: IAM group authentication is available in Preview for new AlloyDB clusters
Note: IAM group authentication is available in Preview for new AlloyDB clusters. To enable this feature on an existing cluster, contact your Google Cloud account team. IAM group authentication for AlloyDB is available in Preview for new clusters running PostgreSQL 15 and later.
AlloyDB write endpoints are now available in Preview
AlloyDB write endpoints are now available in Preview . Write endpoints simplify database connection management by providing a stable domain name service (DNS) name for your applications, decoupling them from instance IP addresses.