Introduction: From Keywords and Joins to Context and Connections

Modern enterprise applications demand more than simple keyword searches and flat relational joins. Traditional database search is limited to exact matches and text keywords – it fails to grasp context or meaning. For example, a query for a “family-friendly spa resort near a beach” might miss relevant results if those exact words aren’t present, even though semantically similar descriptions exist. Likewise, conventional SQL joins or GIS lookups can find rows matching precise conditions (like resorts within 50 miles), but struggle with more contextual logic – such as identifying which nearby resort is most popular among similar customers. In scenarios like personalized recommendations or natural language Q&A, these limitations become clear. Businesses need to search by semantic similarity, leverage proximity-based logic, and provide context-aware answers – capabilities beyond the reach of basic indexes and joins.

Oracle Database 23ai addresses these gaps by integrating three cutting-edge features as first-class citizens in the database: AI Vector Search, Spatial Graph queries (Property Graph Queries), and grounded generative AI. Together, these innovations let enterprise systems retrieve information by meaning rather than just matching words, analyze data relationships through graph patterns (e.g. networks and geospatial proximity), and generate rich insights with large language models that are anchored in trusted data. All this lives in Oracle’s converged database platform, eliminating the need for separate specialized engines. The result is a unified, secure, and intelligent data environment – enabling applications to deliver precise recommendations, location-aware analytics, and reliable AI-driven answers. In the sections below, we’ll explore each of these core features of Oracle 23ai and why they’re transformative for modern data architectures.

Vector Search1
Vector Search – Finding Meaning, Not Just Keywords

One of the most groundbreaking features in Oracle Database 23ai is vector search. In simple terms, vector search lets the database understand conceptual similarity between pieces of data. Instead of looking at raw words or values, data is represented as high-dimensional numeric vectors (embeddings) that capture the semantic content. Two documents, images, or records with similar meaning will have embeddings that are close to each other in this vector space, even if they don’t share keywords. This enables search results based on meaning, not just text matching – a fundamental shift for information retrieval.

Traditionally, implementing semantic search required external AI services or specialized vector databases. Oracle Database 23ai eliminates that complexity by integrating vector capabilities directly into the database engine. It introduces a native VECTOR data type, specialized indexes, and SQL operators for similarity comparisons — supporting multiple distance metrics such as cosine, euclidean, dot product, and more. This allows you to store embeddings alongside your regular data and retrieve the most semantically relevant results with a single SQL query. By ranking results in the ORDER BY clause using the appropriate distance metric, Oracle can efficiently surface the top matches without returning the raw distance value, keeping results clean and user focused. For example, after vectorizing a product description or a support ticket into a 384-dimensional vector, you can query for the top 5 most semantically similar items like so:

SELECT item_id
FROM product_embeddings
ORDER BY VECTOR_DISTANCE(item_vector, :query_vector, COSINE)
FETCH FIRST 5 ROWS ONLY;

In this query, “:query_vector” is an embedding of the search phrase (e.g. the user’s description of what they want), and the VECTOR_DISTANCE function ranks items by semantic closeness. Oracle will efficiently retrieve the items whose content is most similar in meaning to the query – even if the words differ. This approach is transformative for semantic retrieval: it surfaces results that would be missed by keyword search, enabling use cases like intelligent product recommendations, document search by topic, image similarity lookup, and more. In enterprise settings, this capability future-proofs applications to handle unstructured data (text, images, audio) and multilingual content without brittle manual tuning. The meaning is what matters.

VS3

Because Oracle’s vector search is part of the database, it can be combined with all the power of SQL and relational data. You can filter vector search results by other attributes (permissions, timestamps, customer segments, etc.) or join them with structured data in one query. This integration of semantic and business data is unique to Oracle’s approach. As Oracle executive of database technology Juan Loaiza noted, “Searches on a combination of business and semantic data are easier, faster, and more precise if both types of data are managed by a single database.” In practice, a query could find the closest matching support articles to a customer’s issue (via vector similarity) and simultaneously ensure those articles are for the right product and region (via relational filters) – all in one step. Such blended queries eliminate the need for separate AI search services and complex pipelines. The net benefit is highly accurate answers retrieved quickly and securely, using skills your team already has (SQL) on data already in your Oracle system.

In a prototype, a Vacation Club service used Oracle 23ai to recommend travel promotions. The app stored embeddings for resort descriptions and past travel tips. When staff searched for “kid-friendly beach resort with a spa” the database’s vector search found a promotion describing a “family getaway at an oceanfront resort with full-service spa”, even though the phrasing differed. This relevant result was found because Oracle compared the meaning of the request and the data, not just literal words – a capability that significantly improves the quality of recommendations.

vs21

Spatial Graphs – Connecting Data by Location and Relationships

While vector search brings semantic smarts, Oracle 23ai’s Spatial and Graph support (SQL/PGQ) adds a new way to represent and query relationships in your data. A property graph models your data as a network of vertices (entities) and edges (relationships) that can carry properties. Oracle 23ai is among the first databases to support the emerging ISO SQL standard for Property Graph Queries (PGQ) directly in SQL. This means you can create graph views over your tables and query them with pattern-matching syntax – no separate graph database or ETL required.

Spatial graphs leverage this capability to integrate geospatial data and network relationships. Traditional GIS functions can compute distances or find points within a region, and SQL joins can link tables by keys, but answering questions like “Who are the closest customers and which of them influence others?” or “What are the top connected hubs in our supply chain?” becomes cumbersome with pure relational methods. By contrast, modeling these scenarios as graphs makes the queries intuitive and concise. Oracle’s implementation treats location and relationship data as first-class citizens – you can combine spatial calculations with graph traversal seamlessly.

For example, imagine a graph of customers and resorts where an edge “NEAR” connects a customer to each resort within 500 miles of their home. Using Oracle’s PGQ support, finding the nearest resort for a given customer is as simple as querying a graph pattern from that customer node to its connected resort nodes, rather than manually calculating and sorting distances. Here’s what a query might look like using the GRAPH_TABLE function and a pattern match:GQ1

SELECT r.name AS resort_name, e.distance_miles  
FROM GRAPH_TABLE(
  CLOSE_VACATION_GRAPH
  MATCH (o IS VC_OWNER)-[e IS CLOSE_TO]->(r IS VC_RESORT)
  WHERE o.owner_id = :memberId
  COLUMNS (r.name, e.distance_miles)
)
ORDER BY e.distance_miles
FETCH FIRST 1 ROW ONLY;

In this snippet, CLOSE_VACATION_GRAPH is a property graph defined over the customer (VC_OWNER) and resort (VC_RESORT) tables, with CLOSE_TO edges connecting owners to resorts that are within 500 miles (the edge property distance_miles stores the exact distance). The query’s pattern (o)-[e]->(r) finds all resorts r reachable by a CLOSE_TO edge from the specific owner o. We then select the resort name and distance and simply pick the shortest distance result. Under the hood, the database uses its spatial index to evaluate the within-500-miles condition and graph traversal to gather results – but to the developer and data managers, it’s just one elegant SQL query. Oracle’s graph query engine handles the heavy lifting of searching the network. Property graphs provide an intuitive way to extract insights from relationships in data, whether those relationships are geographical, social, hierarchical, or based on any other linkage.

Beyond simple proximity, graph queries unlock “network-aware” analytics that are hard to do otherwise. For instance, you can easily find the most popular nodes or paths by leveraging edge properties. Suppose we maintain a graph of regions connected to resorts with an edge weight for how many customers from that region visited each resort. A PGQ query can directly ask for the top edges from a given region – effectively, “what are the top 3 resorts for customers in region X?” – without writing convoluted SQL joins or subqueries. Oracle 23ai’s support for SQL/PGQ lets you express such questions in a natural pattern form, and the database efficiently evaluates it within the same transactionally consistent store as your operational data. There’s no need to export data to a separate graph database or worry about sync issues. The graph is a different lens on the single source of truth in Oracle.

Why traditional approaches fall short: In the past, achieving these insights meant either doing complex multi-step SQL (joining tables and filtering by spatial functions, then aggregating for popularity) or using specialized graph or GIS tools. Those methods can be slow to develop and hard to maintain. By contrast, Oracle’s spatial graph features make it trivial to answer questions about proximity, connectivity, and influence in one go. This capability is critical as enterprise data grows more interconnected – whether it’s mapping relationships between customers and products, tracing supply chain networks, or analyzing linkages in financial transactions. With Oracle 23ai, you get graph-powered analytics inside the database, benefiting from Oracle’s enterprise-grade performance and security on graph workloads.GQ3

The Vacation Club case study made use of spatial graphs to enhance recommendations. The app built a graph where club members were linked to resorts by “nearby” edges (based on geospatial distance), and regions were linked to resorts by “popularity” edges (number of visits). This allowed the team to query the nearest resorts for a member and the top resorts for that member’s region with minimal SQL. Instead of writing separate queries to calculate distances and perform aggregations, a single graph query found the answer, which the app used to suggest travel options that other similar members enjoyed. The ability to treat location-based relationships as queryable data points simplified the logic and enriched the recommendation with location context.

Answers with Retrieval-Augmented Generation (RAG)

The third pillar of Oracle Database 23ai’s innovation is the integration of generative AI capabilities in a grounded manner. Generative AI (think large language models like GPT) can produce remarkably human-like answers and recommendations from natural language prompts. However, a well-known challenge is that these models can “hallucinate” – i.e. produce incorrect or made-up information – especially when asked about specific, up-to-date business facts. The remedy is to ground the model’s output in real data. Oracle achieves this through a technique called Retrieval-Augmented Generation (RAG), which tightly couples vector search with LLMs to keep the AI’s answers accurate and context-aware.

Here’s how it works: when a user poses a question, the system first uses vector search to retrieve relevant knowledge from the database (this could be product specs, knowledge base articles, recent transactions – whatever context fits the question). These top results are then provided to the generative AI model as part of the prompt. The LLM uses this retrieved context to formulate its answer, ensuring it stays anchored to the truth as known in the database. In Oracle 23ai, this workflow is supported end-to-end. The database can vectorize the user’s question, perform a similarity search across enterprise data, and then feed the results into an LLM invocation (via Oracle’s AI services or an API) – all orchestrated within a unified environment.

The benefit of this grounded approach is twofold: higher accuracy and zero data exposure risk. By augmenting the prompt with private, up-to-date data from your Oracle database, the LLM’s response is far more likely to be correct and relevant to your organization. It won’t guess a number or policy – it will state what the database content provides. This also means you don’t have to fine-tune or retrain the model on your confidential data (which can be costly and risky). instead, the model remains generic but is prompted with your data on the fly. Keep in mind, your data never leaves the safe harbor of the database – only the necessary snippets are passed to the AI at query time.

Retrieval-Augmented Generation (RAG) pipeline using Oracle Database 23ai. In step 1, the user’s question or prompt is converted into a vector. Step 2 uses Oracle’s vector search to find semantically related pieces of data from the enterprise database (e.g. documents, records) that match the query. In step 3, this retrieved data is added to the LLM’s prompt (augmented context) along with the original question. Step 4 sends the combined prompt to a generative AI model, which produces an answer that is grounded in the provided data. This approach ensures the AI’s response is backed by real, up-to-date information from the database, greatly reducing hallucinations and increasing relevance.

RAG

To illustrate, consider an employee asking their company’s chatbot: “What are our current warranty policies for solar panels, and can you summarize any recent updates?” A vanilla LLM might give a generic answer or outdated info. But with Oracle’s RAG pipeline, the database would retrieve the latest warranty document text and any recent policy update notes (via vector similarity search on internal knowledge bases). Those snippets feed into the prompt, and the LLM’s answer will cite the specific current policy details, correctly reflecting the latest changes. The answer is both conversational and grounded in the company’s actual data. If the model tries to drift beyond the provided facts, Oracle’s approach can even instruct it not to. The result is an AI response that enterprise users can trust – because it’s essentially an intelligent synthesis of the organization’s own knowledge.

Oracle 23ai advantage is that it provides the complete toolkit for this solution in one platform. The vector store is built into Oracle Database, so your documents and embeddings live alongside other data securely and can be queried with standard SQL. The database can call out to Oracle Cloud’s AI services or third-party models in a controlled way to get the generative response, often through simple API calls. And all of this happens with Oracle’s governance around security, privacy, and auditing. In practice, this makes it much easier for architects to implement AI features like chatbots, advisors, or report generators that know what they’re talking about. Your LLM can remain a general-purpose genius, while Oracle’s RAG pattern ensures it consults the company’s “brain” (the database) for any specifics. As a bonus, because the retrieved context can include citations (e.g. document IDs or URLs), the system can even point back to sources, adding transparency to AI outputs.

The Vacation Club AI application used Oracle’s RAG integration to generate personalized vacation recommendations for members. When a staff member clicked “AI Recommendation” tab, the app gathered all relevant data about that member – past stays, preferences, current resort promotions – by querying the Oracle database. It then constructed a prompt with that data and sent it to an OCI-hosted LLM. The model responded with a tailor-made vacation plan that referenced the member’s own history and the latest available offers. Importantly, because the LLM’s answer was grounded in live data (retrieved via vector search and graph queries), it did not hallucinate nonexistent resorts or invalid deals; it recommended real resorts that were available and matched the member’s interests. This showcases how vector search + generative AI in Oracle 23ai can turn raw data into useful, contextual advice – essentially delivering an “AI concierge” experience – without compromising on accuracy.

AI Rec

Unified Architecture: AI + Data Together, Not Apart

Underpinning these features is Oracle Database 23ai’s fundamental philosophy of a converged data platform. Instead of fragmenting workloads across specialized databases (one for vectors, one for graph, one for JSON, etc.), Oracle brings it all under one roof. This architectural advantage is critical for enterprises looking to innovate rapidly while maintaining governance. Here are a few key benefits of Oracle’s unified approach:

  • Single Source of Truth: All your structured data, unstructured embeddings, graph relationships, and AI models reside in one database. This eliminates the need to copy data into separate silos. Fewer moving parts mean less data drift and easier enforcement of data integrity and consistency. Your AI queries and your transactional queries both see the same up-to-date data.
  • Less Complexity and Overhead: Adopting Oracle 23ai means you don’t have to stand up and integrate new platforms for vector search or graph analytics. There’s no extra infrastructure to manage or secure – Oracle’s multi-model engine handles it all. This dramatically reduces architecture complexity and operational cost. In addition, developers and DBAs can leverage their existing Oracle skills and tools, rather than learning new systems for each AI task.
  • Unified Security and Governance: Oracle Database’s renowned security features (encryption, RBAC, auditing, Data Vault policies, etc.) extend automatically to these new data types. Vectors and graph data can be secured using the same roles and privileges as your tables. Moreover, since data isn’t moving out to external services or databases, there are fewer points of exposure. This is especially important for RAG scenarios – sensitive business data stays inside Oracle, and only the minimum necessary context is shared with the AI model at runtime. The result is an AI system that complies with corporate data policies by design.
  • Enterprise-Grade Performance & Scalability: Oracle’s vector search and graph query implementations benefit from decades of engineering in optimization, indexing, and distributed execution. The vector index can handle millions of embeddings with low-latency search, and features like Oracle Real Application Clusters (RAC) and Partitioning work seamlessly for vector data. Graph queries are optimized to run in-memory and parallel where possible. And because everything runs on proven Oracle Database technology, you get the reliability and scalability expected of mission-critical systems.
  • Integrated Development Experience: Developers can use Oracle’s standard interfaces (SQL, PL/SQL, REST via ORDS, Oracle APEX, etc.) to incorporate AI search and generation into applications. For example, a SQL query can call DBMS_VECTOR_CHAIN to generate an embedding or use GRAPH_TABLE to run a pattern match, and the results can join with other queries or be returned via a REST API.

By delivering vector search, spatial graph, and generative AI capabilities within Oracle Database 23ai, Oracle has essentially added powerful new “brain modules” to the enterprise data backbone. And we didn’t do so in a vacuum – these features were designed to work together. For instance, a single application workflow can seamlessly query some relational data, perform a vector similarity search for context, run a graph query for additional insights, and then call an LLM all within Oracle, with minimal data movement. Fewer integration points mean not only better performance but also easier maintenance and troubleshooting. This unified approach accelerates innovation which leads architects to focus on solving business problems rather than stitching together disparate technologies.

Conclusion: Future-Proofing Enterprise Data with Oracle 23ai

Oracle Database 23ai represents a significant leap forward in enterprise data management. By integrating AI vector search, spatial/graph analytics, and grounded generative AI into its core, Oracle enables organizations to unlock new levels of insight and intelligence from their data – all while leveraging the robustness of a proven database platform. These features directly address the demands of modern applications, the need to search and recommend by meaning, to understand connections and context in data, and to interact with users in natural language with confidence in accuracy.

For Oracle customers, 23ai offers a path to implement cutting-edge AI solutions (like semantic search engines, recommendation systems, and AI assistants) without reinventing the wheel or compromising on enterprise requirements. Data architects and engineers can enrich their systems with AI capabilities using familiar SQL and Oracle tools, avoiding the complexity of multiple niche databases. Business leaders can appreciate that these innovations come with Oracle’s focus on security, scalability, and data integrity. In competitive terms, adopting such a unified AI-augmented data platform can be a key differentiator – enabling faster development of intelligent features and more personalized, context-aware experiences for end users.

Learn More About Oracle Databases Today

To learn more about Oracle Databases and their latest features, check out the database blog. For hands-on experience, explore the LiveLabs workshops below where you can try out cutting-edge capabilities like vector search, property graphs, and RAG: