What the report you receive looks like
Every audit produces two documents: a board report, readable without a DBA, and a technical report with the matching commands. Here they are in full, with no cherry-picked extract.
What you are looking at, exactly
This example is a real, unretouched output of the platform: the same code produces your reports. The data, however, comes from a demonstration set — the instance, the host name and the measurements are fictional. We do not publish a client's report without their written consent.
The case shown
- Engine
- SQL Server 2016 SP3, Standard Edition
- Role
- Production application server
- Overall score
- 70 out of 100 — average
- Open gaps
- 30, of which 19 are priorities (critical and high)
- Checks run
- 418 read-only checkpoints
A deliberately ordinary case: neither an exemplary server nor a disaster. This is what a small company whose database nobody watches actually looks like — including a version out of support since 14 July 2026.
The deliverable, in full
Board report
Three pages. The score, the four pillars, the risks translated into business language with their level and the effort to fix them. This is the document you present to a board or an insurer.
Technical report
Finding by finding: what was measured, the expected value, the consequence, and the T-SQL fix where one exists. This is your team's working document.
Why two documents and not one
An audit report written for a DBA cannot be presented to a board, and an executive summary cannot be used to fix anything. Most audits deliver one or the other. We deliver both from the same collection, and the control re-audit then measures what was actually fixed.
Your report will look like this, with your numbers
The scope is settled in a 30-minute call, before any invoice.