Find the query that is hurting your database, and the script that fixes it.
dbriq is a monitor and performance advisor for SQL Server, Azure SQL, PostgreSQL and MySQL. It runs on your own Windows PC or server, reads your databases through a read-only login, and tells you in plain words what is wrong and what to do about it.
Free beta for Windows 10 and 11, 64‑bit.
OrderBatchService opened a transaction 33 seconds ago and isn't running anything, so it hasn't been committed. The longest wait is 22 seconds.
The answers, not just the graphs
dbriq reads waits, execution plans and history across every server you add, then says what is wrong, which queries are responsible, and how to fix it.
Why is it slow?
- Performance advisorNames the bottleneck (CPU, storage, log writes, memory, blocking, plan regressions), the queries behind it with their share of the load, and fix scripts you review and run yourself.
- Response timeActive sessions are sampled every 2 seconds and classified by wait, so you see which queries spent the time and what they waited on.
- Execution plansA graphical plan laid out like SSMS, explained in sentences, with missing indexes, key lookups, spills and implicit conversions called out.
- Time travelClick any point on a chart to see what was running and who was blocking whom at that moment.
What is about to break?
- Health checksBackups against your RPO, CHECKDB, Availability Group and geo-replica lag, failed Agent jobs, configuration and security best practices, and end-of-support dates.
- Locks and deadlocksLive blocking chains, blocking history, and deadlocks grouped into recurring patterns, each with a lock graph and a step-by-step account.
- Storage forecastsDatabases, elastic pools, disks and Managed Instance storage that will fill up at the current rate of growth.
- Alerts that know what normal looks likeBaselines per weekday and hour, maintenance windows, and routing to Slack, Teams, PagerDuty or any webhook.
What do I report?
- InventoryOne database, a whole server or the full estate as a printable HTML report or an Excel workbook.
- Health reportWhat happened on a server in the last 24 hours or 7 days: alerts, blocking, deadlocks, changes and top queries.
- ComplianceA security audit per server, and a report for auditors with controls, evidence and a sign-off block.
- Index and cost reportsUnused, duplicate and missing indexes, parameter sniffing, and right-sizing with the monthly saving.
See it before you install it
Real screens from dbriq running its built-in demo: seven servers and 96 databases with problems built in. The installed app opens with the same demo, so you can look around before adding a server.
Every database on one page, sorted by risk. Healthy databases are hidden until you ask for them, and each problem row says what is wrong.
Only the databases that need attention, most urgent first, each with its problem in words and a trend line.
A database page: active alerts, the diagnosis, the session or query causing it, recent changes that may explain it, and fix scripts.
The execution plan of a running query with actual rows so far, what it does in plain sentences, and the operator where the cost is.
The inventory report for a server, ready to print to PDF or download as an Excel workbook.
Works with the databases you already run
On-premises, in VMs and in the three big clouds. Up to 100 servers in one installation.
| Engine | Where it runs | What dbriq reads |
|---|---|---|
| SQL Server | SQL Server 2016 SP2 and later on-premises or in VMs, Azure SQL Managed Instance, Amazon RDS for SQL Server, Google Cloud SQL | Instance-wide DMVs, Query Store, msdb history |
| Azure SQL Database | Single databases and elastic pools | Per-database CPU, IO and log use, plus each database’s DMVs |
| PostgreSQL 10+ | Self-hosted, Azure Database for PostgreSQL, Amazon RDS and Aurora, Cloud SQL | pg_stat_activity, pg_stat_statements, table statistics |
| MySQL and MariaDB | MySQL 5.7 and 8.x, MariaDB, Azure Database for MySQL, Amazon RDS and Aurora, Cloud SQL | performance_schema digests and waits, InnoDB lock waits |
PostgreSQL and MySQL don’t report CPU through SQL, so dbriq ranks their queries by share of database time.
Your data stays on your network
dbriq sees query text and server details, so it is built to keep them where they are.
Runs where you install it
dbriq is a Windows app, or a team server on your own Windows or Linux machine. Metrics and query text are stored there. The app sends nothing to us.
Read-only by design
The setup scripts create a monitoring login with only the permissions it needs. Fix scripts are shown for you to review and run; dbriq never runs them.
Passwords stay encrypted
Server passwords are kept in Windows Credential Manager or an encrypted vault, never in the configuration file.
AI only when you ask
“Explain with AI” is optional and needs your own Claude API key. It sends the finding and the query with every literal value replaced by a question mark.
Getting started
Create an account
Free, with your work email. Confirm it from the email we send.
Install dbriq
Run dbriqSetup.exe on Windows 10 or 11. No administrator rights needed. It opens with demo data so you can look around first.
Create the monitoring login
Run
setup_monitoring_user.sql, or the PostgreSQL or MySQL script, on each server. The scripts are in the Start menu under dbriq.Add your servers
Open Servers, choose Add server, test the connection, and dbriq starts collecting. Findings appear within minutes.
Questions
Is the beta free?
Yes. Create an account and download it; there is nothing to pay during the beta.
Should I point it at production servers?
Start with a non-production server, as you would with any new monitoring tool. Monitoring queries are read-only with a 30-second timeout, and reports run on short connections with a 5-second lock timeout and low deadlock priority. Once you are comfortable with what it does, add production.
Does dbriq change anything on my servers?
No. It reads system views and never runs the fix scripts it suggests. The only thing it creates is a temporary one-minute capture session if you run the client timeouts report without the optional always-on session, and it drops that session afterwards.
What does it need on my computer?
Windows 10 or 11, 64‑bit. For SQL Server you also need Microsoft ODBC Driver 18 for SQL Server; SSMS and Azure Data Studio usually install it already, and the installer offers the download if it is missing. PostgreSQL and MySQL drivers are built in.
Can my whole team use it?
Yes. dbriq can run as a team server behind HTTPS with sign-in, roles (viewer, operator, admin), access limited to particular servers or databases, and single sign-on through your reverse proxy. Email support@dbriq.com for help setting it up.
Is there a Mac or Linux version?
The desktop app is Windows only. The team server also runs on Linux in Docker, and the dashboard works in any modern browser.
How do I report a bug or suggest a feature?
Email support@dbriq.com with what you saw and the dbriq version from the installer. Please send security issues to security@dbriq.com.
Try dbriq on your own servers
Free during the beta. Windows 10 and 11, 64‑bit.