Know your risk
in plain English.
Your servers are running fine. You know that. What you might not know is what's quietly sitting underneath, waiting.
We've taken the 2:39am call. The point of the check is so you don't have to.
Three steps, no install.
Tell us your instance count
Thirty seconds — the form above. Roughly how many SQL Server instances, and where to send the report.
We run a read-only 500+ check scan
Powered by SQLTriage. Configuration and usage metadata only — no writes, no agents left behind, no production impact.
You get a graded report, in plain English
The risks that actually matter, ranked, each with a next step — backups, security, patching, configuration and licensing. Usually back within a couple of business days.
A script tells you what's wrong. This tells you what to do.
You can absolutely run a free script — sp_Blitz and the First Responder Kit are excellent, and the engine behind this check reads their output directly. The difference is what happens next: instead of a raw priority list, you get a graded report that ranks the findings by real business risk, maps them to the standards you're measured against, and hands you a next step for each — read by a specialist who has fixed these before, not just printed by a tool. Here's the full comparison.
What people ask before booking a check.
How long does it take?
The scan itself is read-only and quick. We usually have the graded report back to you within a couple of business days — sooner for a single instance.
Will it touch production?
No. The health check is read-only by default. We look at configuration and usage metadata, change nothing on your servers, and leave no agents behind. You see exactly what we run.
What do I actually get back?
A graded report in plain English: a health score, the top findings ranked by real risk, and a clear next step for each — across backups and recoverability, security and access, patching, configuration and licensing. Not a wall of red.
Is it really free? What is the catch?
It is genuinely free, and there is no catch. The engine behind it, SQLTriage, is free and open source. The findings are yours whether we ever work together or not — no obligation, and no sales follow-up unless you ask for one.
How is this different from a free script like sp_Blitz?
A free script tells you what is wrong; this tells you what to do about it. SQLTriage imports sp_Blitz output and adds the grading, the risk ranking and a plain-English report — read by a specialist who has fixed these before, not just printed by a tool.
What happens after the report?
That is up to you. Most people fix the urgent items themselves, with the report as the plan. If you want help, we tell you what it costs before you commit — but the check stands on its own.