SQL databases
Set up read access to PostgreSQL, MySQL/MariaDB and SQL Server — with a technically enforced restriction to SELECT.
Kasimir can access your SQL databases read-only: list tables, look at their structure and run queries for analysis — in the chat and in agents. Writing is ruled out, not by agreement but technically.
Connect a database
Open Customize → Integrations and click the SQL databases tile (or go straight to /sql). In the dialog you enter:
Field | Meaning |
|---|---|
Name | What the database should be called in Kasimir, e.g. “Production reporting” |
Engine | PostgreSQL, MySQL / MariaDB or SQL Server |
Connection DSN | The connection string, e.g. |
Visibility | Only me (any member may create it), company-wide (owners and admins only) or project-wide (the project's owner and managers, plus company owners and admins) |
The DSN is tested once when saving and then stored encrypted. It is never shown again afterwards — not even to you. Use Test connection to check beforehand; if it succeeds, Kasimir reports how many tables were found.
Ideally, create a dedicated user with read-only rights in your database and use its credentials. Kasimir enforces read queries, but a restriction on the database side is the more robust boundary.
What is possible in the chat
Kasimir can:
list connected databases
show the tables of a database
show the columns and types of a table
run a read query
In the chat you switch a connected database on under Knowledge sources → Databases; Kasimir can then query it read-only. By default Kasimir asks before each query (Ask first).
Read-only
Kasimir only runs read queries; anything that would change data or structures is rejected. On SQL Server, WITH queries (CTEs) are not possible either – write them as a subquery.
Limits of a query
A query returns at most 200 rows. If the result is cut off, Kasimir says so in the answer — so you can see when the result is incomplete and narrow the query.