SQL Server audit · Databreizh

Your application runs on SQL Server.Who is watching it?

If the answer is "nobody", here is what we find most often.

  • Criticalbackups that were never restored
  • Highcustomer data left unencrypted
  • Mediuman engine with no security patch

SQL Server since 2001418 control pointsSQL Server 2012 to 2025report published in fullread-only collector

The proof, right away

Here is a complete report. In full. No form.

This is not a mockup: it is real product output, published as-is — a board report and a technical report, in French and English.

Here is a complete report. In full. No form.
Security48 / 100Critical
Performance83 / 100Good
Resilience53 / 100Poor
Operations65 / 100Poor
Open the report

Don't trust us. Take away our ability to do harm.

Every query the script can run is published. All of them read-only — and the delivery pipeline fails if a single one is not.

-- SEC012 · compte de service du moteur
SELECT TOP 1
    ISNULL(service_account, '') AS service_account,
    ISNULL(startup_type_desc, '') AS startup_type_desc
FROM sys.dm_server_services
WHERE UPPER(filename) LIKE N'%SQLSERVR.EXE%'

Real excerpt from the collector: no writes, no network calls.

  • Read-only, verifiable query by query
  • Three privilege tiers: you choose what we may read
  • Nothing installed, no agent, no inbound connection

You receive the script before the audit: your DBA reads it in full, before we run anything at all.

What we find, and what it costs

  • Critical

    The backup runs. Nobody has ever restored it.

    The day you need it, you discover it is unusable. Days of data entry gone.

  • High

    Customer data sits unencrypted on disk.

    One stolen drive or one misplaced database copy, and you are notifying the regulator within 72 hours.

  • Medium

    The engine has had no security patch for two years.

    The known vulnerabilities are public. Your cyber insurer will ask.

What it asks of you: almost nothing

  1. 01

    Scoping call

    30 min

  2. 02

    You run the script

    ~5 min

  3. 03

    I analyse

    48 h

  4. 04

    Video debrief

    1 h

Nothing installed on your servers. No agent. No inbound connection.

What you receive

Your score, out of 100.

Plus the breakdown by domain, the drift since the last audit, and an action plan ranked by risk and effort.

  • Board report · PDF
  • Technical report · PDF
  • Online workspace

One mission, one follow-up, one workspace

Prices upfront, scope agreed together in a first call.

Starting point

Expert-led audit

from€1,490
one-off mission · excl. VAT

A complete assessment of your SQL Server instances, led by an expert and presented to your management as well as your teams.

  • Collection on your instances (418 checks)
  • Expert analysis and risk prioritisation
  • Management report + technical report
  • Readout call with the expert
  • Platform access for 12 months: dashboard and history
Request an audit

Advisory follow-up

from€500/ month
6-month engagement · excl. VAT

Your SQL Server expert stays on the job: watching for drift, re-auditing every quarter and alerting you before things break.

  • Monthly drift check: collection re-run, gaps commented
  • Full expert re-audit every quarter
  • Up to 2 h of contact per month with your named DBA
  • Alerts on critical drift

Reserved for fleets audited within the last 12 months.

Talk to an expert

Partner workspace

By quote

For independent DBAs and managed service providers: audit and follow all your clients from a single workspace.

  • Multi-client portfolio
  • API and webhooks
  • Management and technical reports per client
  • Partner terms: a discount on the public grid, public price honoured with the end client

The subscription depends on how many clients and instances you follow.

Contact us

See the full pricing details

Prices in EUR, excl. VAT. Firm grid up to 20 instances; above that, by quote. The scope is agreed during a first 30-minute call.

Who runs the audit

Gurvann Guennegues

Independent SQL Server expert · since 2001, from version 6.5 to 2025

Currently the SQL Server technical lead on an international programme for a CAC 40 group, previously head of a DBA team at an investment bank. The collector measures; I read your results, decide what matters in your environment and explain it to you.

LinkedIn profile

The questions we get asked

The ones executives ask, and the ones asked by the IT person they forward this page to.

Can the collector change anything on my production server?

No. It performs no writes on your databases: no CREATE, no ALTER, no DROP, no INSERT, no UPDATE, no DELETE. Its queries run without taking locks, so it cannot slow your application down. This is not a statement of intent: on every change to the collector, the delivery pipeline analyses the entire body of queries and refuses to ship if a single one is not read-only — or if a single one could not be extracted for review.

Can we review the queries before letting them run?

Yes, and it is built for that. One collector option writes every query it can run into a .sql file, each with its check identifier and the matching line of the script. That command does not connect to SQL Server, needs no privileges and runs no audit: the script analyses itself, then stops. You hand the file to your DBA or your security officer. The collector is plain PowerShell — no binary, no obfuscated code.

What privileges do you need on the server?

As few as possible, and you decide. The default tier is a login that can only read server state, metadata and the msdb history: it reaches the contents of none of your business tables. Two broader tiers exist to cover more checks; the broadest one requires sysadmin and is therefore no longer read-only by construction — it is disabled once the audit is done. In every case, the result names what could not be assessed for lack of privileges, and why.

How much of my time does this take?

Two meetings and five minutes of hands-on work. A 30-minute scoping call up front, a one-hour video debrief at the end, and in between you run the script yourself. Nothing to install on your servers, no agent, no inbound connection. The analysis and the writing are on our side; the debrief is scheduled within five business days of the collection reaching us.

What exactly do I receive?

Two PDF reports: the board report, in plain language, readable without a DBA, and the technical report with the matching T-SQL commands. With them, your score out of 100, the breakdown by domain, and an action plan ranked by risk, by effort and by score points recovered. The results stay available in an online workspace, and the video debrief is there to settle priorities with your team.

How much is it, and what makes the price move?

From €1,490 excl. VAT for a single instance. What moves the price is the number of SQL Server instances to audit, not the number of days spent. Every tier is a fixed package: the quoted price is the final price, no day is billed separately, and the price per instance falls as the fleet grows. The scope is settled in the first call, before any invoice.

Where does my data go?

The collector reads no business data: only system catalogues and engine metrics. What it produces is a file of configuration facts and findings, and nothing leaves your environment automatically — you are the one who sends it to us. The platform is hosted in France, with a European provider: your data never leaves the EU. Findings and personal data are encrypted at rest, your data is neither sold nor rented, and your organisation stays in charge of how long it is kept and when it is deleted. The detail is in the privacy policy.

Why pay, when free tools exist?

They exist and they are good: Microsoft publishes one, and so does the SQL Server community. They produce raw data you have to know how to read — in other words, they assume a DBA. What you pay for here is not the collection, it is the interpretation: an expert reads your results, translates them into risk for your business, ranks them by priority and explains them to you. If you have a seasoned SQL Server DBA in-house, a free tool may well be enough.

What happens after the audit?

You leave with an action plan ranked by priority, which your team carries out. Applying the fixes is not part of the audit: that is a separate engagement, by quote. Three to six months later, a control re-audit measures what actually held. And if you want to stay covered over time, the advisory follow-up re-audits regularly and keeps the action plan up to date. None of this is compulsory: the audit stands on its own.

Knowing takes 30 minutes. Not knowing can cost you days.