Databases

Connect a database and anyone in the workspace can ask it questions without writing SQL: “who are our top five customers by order value?” The AI reads the schema, writes the query, runs it and turns the result into a table and a takeaway. Every query it ran is one click away, so the answer is always checkable.

app.stickyprompts.com Screen recording

Supported databases

MySQL, MariaDB, PostgreSQL and SQL Server. Microsoft Power BI appears under Databases & BI as Coming soon. You can connect as many databases as you need.

Before you start

Do these two things on your side first. They are what make the connection safe.

1. Create a dedicated database user for StickyPrompts with the least privilege that works - for most teams, read access to the tables people will ask about and nothing else. Never reuse an admin or application account.
2. Make the database reachable. Either allow StickyPrompts’ IP address in your firewall, or use the SSH bridge (below) if the database lives on a private network.

188.245.64.188

That is the address every StickyPrompts database connection comes from. Allow it on the database port, and only it.

Connect a database

1. Open Add connection and pick the database

   Go to Integrations, select Add connection, choose Workspace (shared with everyone) or Personal (just you), filter by Databases & BI and select MySQL, MariaDB, PostgreSQL or SQL Server. Only workspace owners and admins can add workspace connections.

2. Describe it

   Give it a name and a description people will recognise, such as Northwind Retail DB and Orders, customers and products for the retail stores.

3. Enter the connection details

   Field	What to enter
   Host	The database server’s address. If you use the SSH bridge, the address as seen from the jump host, usually localhost.
   Port	Usually 3306 for MySQL and MariaDB, 5432 for PostgreSQL, 1433 for SQL Server.
   Database	The database name.
   Schema	Optional. PostgreSQL uses public and SQL Server uses dbo if you leave it empty.
   Username and password	The dedicated StickyPrompts user.
   SSL mode	Require, Verify CA, Verify full or Disable. Use Verify full when your server has a certificate you can verify; never Disable over the internet.

4. Choose the permission level

   Pick Read only unless you have a specific reason not to. See Permission levels.

5. Test and save

   StickyPrompts connects to your database with these details before it saves. If it cannot reach the server or sign in, you see the error and nothing is saved. Once saved, the database appears under Databases & BI with its permission level on the card.

   app.stickyprompts.com/integrations 1 Permission level 2 Shared with the workspace

Permission levels

Level	What the AI may run
Read only	One SELECT (or WITH ... SELECT) statement at a time. Anything else is refused.
Read & write	SELECT, plus INSERT and UPDATE.
Full access	Anything your database user is allowed to run, including DELETE, DROP and schema changes.

Read only checks every statement before it runs and rejects anything that is not a single read. Because the check looks for words like update or delete anywhere in the SQL, a harmless read that contains one of those words - a column called update_note, for example - can be refused. Rephrase the question, or ask the AI to avoid that column.

Reach a private database with the SSH bridge

If your database is not reachable from the internet, StickyPrompts can connect through an SSH jump host (bastion) that can reach it.

1. Turn on the SSH bridge

   In the database connection form, enable the SSH bridge and enter the jump host’s SSH host, SSH port (usually 22) and SSH username.

2. Authorise StickyPrompts' key on the jump host

   The form shows a public key. Add it as one line to ~/.ssh/authorized_keys for that SSH user on the jump host:

   jump host

   $ echo 'ssh-ed25519 AAAA...copied-from-stickyprompts' >> ~/.ssh/authorized_keys

   $ chmod 600 ~/.ssh/authorized_keys

   Only the public key is shown. The private key never leaves StickyPrompts.

3. Point the host at the database from the jump host's view

   Set Host to the database address as the jump host sees it: localhost if the database runs on the jump host itself, or its private address on your network. Allow 188.245.64.188 to reach the jump host’s SSH port.

Ask questions

Ask the way you would ask an analyst. Mention the database if you have more than one.

From our retail database: who are our top 5 customers by total order value,
and what share of revenue do they make up? Table plus one takeaway.

Which products sold fewer than 10 units last month in the retail database?

The AI first lists your database connections, then reads the tables and their columns, then runs one or more queries, reasoning between steps. Expand the actions line above the answer to see each call and the SQL it ran.

app.stickyprompts.com/conversations 1 Reads the schema first 2 Open to see the SQL

Troubleshooting

Problem	What to check
Cannot connect	Is 188.245.64.188 allowed through your firewall, on the right port? Is the host reachable from the internet, or do you need the SSH bridge?
SSL errors	Your server may not support SSL, or its certificate may not match the host name with Verify full. Try Require to confirm, then fix the certificate.
SSH bridge fails	Is the public key on one line in authorized_keys for the right user? Is Host the address as the jump host sees it?
A read query is refused	See the note under Permission levels about words such as update inside a read.
The answer looks wrong	Expand the actions and read the SQL. Tell the AI what to change (“count only completed orders”) and ask again.

Related