DatabasesMenú de la documentación

Knowledge sources

Databases

Connect PostgreSQL, MySQL, SQL Server, Oracle, Snowflake, SAP HANA or SQLite so agents can answer questions with live SQL queries.

La documentación está en inglés y turco, como la interfaz de Harmona. Esta página se muestra en inglés.

A Database connection lets agents answer questions from live data. The agent turns the question into SQL, runs it against your database and explains the result. Nothing is copied: every answer uses the data as it is at that moment.

Supported databases

DatabaseWhat you enterDefault port
PostgreSQLHost, port, database name, username, password, schema (default `public`)5432
MySQLHost, port, database name, username, password, optional schema3306
Microsoft SQL ServerHost, port, optional instance (for example `SQLEXPRESS`), database name, username, password, schema (default `dbo`)1433
OracleHost, port, service name (for example `ORCL`), username, password, optional schema1521
SnowflakeHost, port, database name, warehouse (for example `COMPUTE_WH`), username, password, optional schema443
SAP HANAHost, port, username, password, optional database name and schema30015
SQLiteThe `.db` database file—

Oracle needs no extra driver on your side.

Connect a database

  1. 1Go to Studio → Connections, click Create Connection and choose Database.
  2. 2Pick the Database Type, then enter a Connection Name and a Description.
  3. 3Fill in the connection details. The port is filled in for you.
  4. 4Click Create Connection.
  5. 5When Harmona asks Analyze this database?, click Analyze database, or Not now to choose tables first.
Make sure the database is reachable from Harmona and the user you enter has the permissions it needs.

Tables and descriptions

Before an agent can answer anything, Harmona reads the schema and writes a description of every table and column. Agents use these descriptions to write correct queries. The analysis costs model usage in proportion to the size of the schema.

  • Update analysis analyzes new and out-of-date tables only. This is usually enough.
  • Choose tables… under More analysis options lets you pick specific tables, then click Analyze selected.
  • Analyze from scratch re-runs every table. Your own edits are kept either way.

Open a table to read its description and column details. Click a description to edit it. Each column shows how sure the analysis is:

BadgeMeaning
VerifiedA query against your data confirmed the description.
Needs reviewThe column stayed ambiguous. The description is a guess, and correcting it improves every answer that uses the table.
EditedA person wrote it. Re-analyzing keeps it.

Short or cryptic names like `ord_amt` or `cst_flg` are where your edits help most. A clear connection Description helps too: it gives the analysis the business context behind the names. To remove a table from the connection, click Deactivate Table.

Atención

Deactivate Table deletes the table's custom descriptions, including the ones you edited, and agents can no longer query it.

Use a read-only user

Agents are instructed to run only SELECT queries, and the tiles a Worker saves only read.

Give Harmona a read-only user

Instructions are not permissions. Connect with a database user that can only read (SELECT), and only on the schemas and tables agents should see. It is the safest setup, and it keeps answers focused.

The model that writes table descriptions is set under Management → Organization Settings → General: SQL analysis model, and SAP HANA analysis model for HANA, whose schemas are often larger. See Deep document analysis.

Actualizado 2026-09-24