Connect SQL Server to AI and ask in plain English
Connect SQL Server to AI with AgentUI, and anyone on your team can ask "which orders shipped late last week?" and get the rows back, not a CSV to clean up. The AI writes the query and runs it against your database. When an answer is worth keeping, it becomes a dashboard your team opens every morning.
Read-only. Revoke access in two clicks.
How connecting SQL Server to AI works
Connect the database
A SQL Server you can already reach online connects through the SQL Server integration. A server in the office gets a small connector that dials out over HTTPS, so no port is opened.
Ask in your own words
Type the question the way you'd ask a colleague. The AI turns it into a SQL query against your tables, runs it, and shows you the rows.
Keep what's useful
Save the answer as a dashboard or an app that refreshes from SQL Server on its own, so nobody rebuilds it next month.
Questions teams ask their SQL Server once AI is connected
The data is already in SQL Server, inside your ERP, accounting or warehouse system. What's been missing is a way to ask without waiting for the one person who writes SQL. These are the kinds of questions people start with:
- Which customers haven't ordered in the last 60 days?
- What's below its reorder point, by warehouse?
- How many shipments went out late this week, compared with last week?
- Which invoices are more than 30 days overdue, grouped by sales rep?
From one answer to a dashboard the whole team uses
A good answer usually needs to be seen again. Turn it into a dashboard that refreshes from SQL Server on its own, so the monthly report stops being a day of copy-paste into Excel.
- Role-based access, so the warehouse lead sees stock and finance sees invoices
- An audit log of who changed a dashboard, and when
- One login for the whole team instead of a spreadsheet emailed around
Is it safe to connect SQL Server to AI?
It's the first thing your IT team will ask. Here's how the on-prem connector answers it:
- It can only read. It runs SELECT and WITH queries and rolls each one back when it finishes, so the AI can't change a record.
- Nothing is copied or synced. Rows go to the person who asked, and the database stays on your server.
- The database password never leaves that server. On Windows it's stored encrypted.
- Revoke the connector and its key stops working within 25 seconds.
What it won't do
- The on-prem connector reads Microsoft SQL Server only. MySQL, PostgreSQL and Oracle need a different integration.
- Each query returns up to 1,000 rows and runs for up to 30 seconds. That's plenty for answers and dashboards, and too small for exporting a whole table.
- It won't write back to SQL Server. Updates still happen in your ERP or source system.
What happens after you connect
Your IT person gets a Word setup guide with screenshots in their language, and installs one service on the server. If they'd rather not do it alone, one of us joins the call. After that you build by describing what you want, and a real person stays on your account, so the tool doesn't end up depending on one employee.
Go deeper
Ask your SQL Server something today
SQL Server connections come with the Team plan and up. If IT wants a person on the setup call, book one.
Read-only. Revoke access in two clicks.