Working with Public LLMs

This topic provides an overview of interaction with DB Assistant module when using a public LLM.

To use public LLMs for interacting with your database and get insights to your code and data set in a conversational manner:
  1. Start by selecting a database connection for which you require AI assistance from the banner of the DB Assistant window.
  2. Next, select the Public LLM option from the drop-down list displayed on DB Assistant window banner.


    Public LLM mode

  3. When you select Public LLM mode for the first time, a disclaimer message is displayed for your review that you must read and then click Continue to proceed.


    Disclaimer Message for new connection_Public LLMs

  4. From the DB Assistant window drop-down fields, select the AI Profile and the Language Model you want to use.


    DB Assistant window in Public LLM mode

  5. Start typing your inputs in the DB Assistant chat box or click the + New Chat icon to start conversing with the DB Assistant in a dedicated chat thread and press Enter (or click the Submit icon).

Sample Interaction with DB Assistant

The following example cites a common interaction with the DB Assistant using Google Gemini-1.5-Flash AI model.

Start typing an input prompt in the chat box and press Enter (or click the Submit icon). The selected public LLM is invoked.


DB Assistant - Sample Query

Based on your inputs, the database and workspace integration is provided through MCP services, and the database information from the specific connection is fed to the LLMs. The integration is done through invoking certain MCP tools which act as third-party models, where you can manage the access of these tools by approving (Allow/Allow All) or blocking (Deny/Deny All) their access to the language models being used.


DB Assistant - Sample response

The AI agent may ask for confirmation for accessing the DB information such as the follows:
  • Metadata information (including database metadata, table metadata, schema metadata, view and program metadata).
  • Database connection configuration information.
  • View (including views, materialized views, JSON relational duality views) and Program source code access.
  • SQL consoles, source code editors and data editors in the IDE.