Via proactiveinvestors.com
A new AI agent lets enterprise users query Oracle databases in plain English, no SQL required
Oracle and Google Cloud have deepened their partnership, and the headline feature is something database administrators have wanted for a long time: a way for regular humans to ask questions of enterprise data without writing a single line of SQL.
The announcement came on April 22, 2026, at Google Cloud Next 2026, and it centers on the Oracle AI Database Agent for Gemini Enterprise.
What actually changed #
The new agent plugs Google’s Gemini models directly into Oracle databases, letting users query complex enterprise data through plain language prompts.
Oracle is also expanding the availability of its Exadata and Autonomous Database services on Google Cloud infrastructure, broadening the surface area of what joint customers can access without leaving the Google Cloud environment.
The overarching product, Oracle AI Database@Google Cloud, runs Oracle Cloud Infrastructure database services directly inside Google Cloud data centers. That’s the key architectural point: enterprises are not routing data back and forth between two clouds. The compute lives where the data lives.
How we got here #
This announcement did not come out of nowhere. Oracle and Google formed the underlying multicloud partnership on June 11, 2024, giving Oracle Cloud Infrastructure database services a home inside Google Cloud for the first time.
A further round of services was added on October 14, 2025, expanding the joint catalog before this week’s AI-focused update.
The April 2026 announcement layers Google’s Gemini AI stack on top of that existing infrastructure foundation, which is the logical next step. First you get the data running on shared infrastructure. Then you build intelligence on top of it.
What this means for the market #
The natural language querying angle lowers the skill barrier for data access, meaning Oracle and Google can pitch these services to a broader set of buyers inside an enterprise, not just the IT department but finance teams, operations, and executives who would never touch a database directly.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our