Built by a DBA, for the people who keep databases running.
dbriq comes from twelve years of looking after SQL Server and Azure SQL databases in 24x7 production, and from knowing how long it takes to find out what is actually wrong.
Why I built dbriq
I’ve been a database administrator for twelve years, looking after SQL Server and Azure SQL databases that can’t go down. Over that time the estates grew: more servers, more cloud, more teams depending on them. The day-to-day monitoring didn’t keep up.
The hard part was rarely the fix. It was finding the problem. An alert would say CPU was high or a job had failed, and then the real work began: which query, which session, what changed, and what is the safe thing to do about it. That meant jumping between tools, running my own scripts, and piecing the answer together under pressure.
dbriq is the tool I wanted on every one of those days. It watches the whole estate, and when something goes wrong it says in plain words what the bottleneck is, which query or session is behind it, why it is slow, what changed shortly before, and the script that fixes it. It never runs that script for you. That decision stays with the DBA.
dbriq is in beta now, and the people using it shape what comes next. If something doesn’t work the way you would expect on your servers, I want to hear about it.
Vinay Yegineni, founder
What twelve years in production put into dbriq
Most of dbriq’s checks come from problems I have solved by hand. Each area below shows where that experience turns up in the tool.
Performance tuning
Indexing strategies and execution plan analysis that cut query times by up to 40%.
In dbriqThe execution plan explorer, and the advisor’s explanation of why each query is slow.
Moving to Azure
Migrating on-premises SQL Server to Azure SQL Database and Managed Instance, for better scalability at lower infrastructure cost.
In dbriqFull support for Azure SQL Database, elastic pools and Managed Instance, with right-sizing advice.
High availability and recovery
Always On Availability Groups, failover clusters, log shipping and replication across multi-node clusters.
In dbriqHealth checks for Availability Groups, geo-replica lag, backups against your RPO, and CHECKDB.
Automation
PowerShell scripts and SQL Agent jobs that take routine work off the team and cut manual intervention.
In dbriqAgent job failure checks, and a copy-ready fix script for every finding.
How dbriq is built
Your servers stay yours
dbriq runs on your own PC or server and connects with a read-only login. Nothing it collects is sent to us.
Advice, not autopilot
Every finding comes with a fix script to review. dbriq never changes anything on your databases.
Plain words first
A finding should say what is wrong and what to do, the way an experienced DBA would explain it to a colleague.
Light on production
Monitoring queries are read-only with short timeouts, and reports run on short connections with a low deadlock priority.
Talk to me
Questions, bugs or ideas: write to support@dbriq.com. It comes straight to me.