productionMicrosoft SQL Server 2016 (SP3)Standard Edition (64-bit)srv-app-01.atlantique.local
47
Global health score
CriticalF
out of 100
Out of support: −10 pointsMicrosoft support for this version (mainstream and extended) has ended: the overall score loses 10 points, then cannot exceed 79 ("Fair" band). A declared ESU does not change the score.
First audit — no trend yet
Audit performed on18 September 2026
Document generated on25 September 2026
Collector4.12.0
SQL Audit PlatformSRV-APP-01
Executive summary
25 check(s) not applicable to SQL Server 2016 — Details at the end of the report.
47
Global health score
CriticalF
Out of support: −10 pointsMicrosoft support for this version (mainstream and extended) has ended: the overall score loses 10 points, then cannot exceed 79 ("Fair" band). A declared ESU does not change the score.
First audit — no trend yet
Security
48/100
Performance
83/100
Resilience
53/100
Operations
65/100
262Compliant
31Gaps
1Warnings
10Critical
9High
Microsoft support SQL Server 2016 — Support ended — July 2026. Paid ESU possible until July 2029, except Express.
90
Technical security posture — CIS SQL Server L1 (sample)
55 compliant control(s) out of 61 evaluated
These controls also contribute to GDPR (Art. 32) and NIS2 (Art. 21) technical measures.
Conformity rate over the sample of CIS controls tested by the platform — not coverage of the full CIS benchmark.
Top business risks
Translated into business language, ranked by stakes. Risk is expressed as a level (High / Medium / Low) and an effort, with no financial figure.
1
Your backups won't protect you from a failure or an attackCritical
In case of disk failure, corruption or ransomware, you risk losing data with no way to restore it.
Risk level CriticalEffort High
Recommended action Schedule log backups every 15-60 minutes depending on RPO
2
Your database is exposed to unauthorized accessCritical
A security gap can allow theft or leakage of your customer and business data.
Risk level CriticalEffort Low
Recommended action Disable the SA account and create dedicated named accounts for the administrators — the SA account is a prime target for brute-force attacks. Quick fix, low risk (check beforehand that no application connects with it).
3
Your database could go down without guaranteed recoveryCritical
If your service continuity isn't guaranteed, an outage can halt your operations for hours or days.
Risk level CriticalEffort High
Recommended action Run a full integrity check of the database, determine the extent of the corruption, then restore the pages or the database from a healthy backup — untreated corruption leads to data loss. Urgent action, high risk (get expert assistance before attempting any repair).
4
The server configuration deviates from best practicesCritical
Unsuitable settings can undermine the stability, security or performance of your database.
Risk level CriticalEffort Low
Recommended action Cap the maximum server memory, reserving RAM for the OS (starting rule: total RAM - 4 GB, or - 10% above 16 GB) — without a cap, SQL Server can starve the system and cause swapping. Quick intervention, low risk.
5
Your sensitive data is not encryptedCritical
If files or media are stolen, the data stays readable and GDPR compliance is not ensured.
Risk level CriticalEffort High
Recommended action Back up each TDE certificate together with its private key and keep them off-server in a secure vault — without this backup, an encrypted database becomes unrecoverable after a disaster. Quick to do, low risk (be sure to protect the key password).
6
Regular database upkeep is not in placeCritical
Without maintenance, data issues go unnoticed and worsen over time.
Risk level CriticalEffort Medium
Recommended action Schedule a weekly integrity check (CHECKDB) on every database — it is the only way to detect silent corruption early, before it spreads to the backups. Moderate effort, low risk.
SQL Audit PlatformSRV-APP-01
Technical annex — detailed results
Detailed gaps and warnings by domain, with the recommended remediation guidance.
S
Access securityWho can reach the database and what they may do there.
6 Gaps · 1 Warnings · 84 Compliant
SEC001SA account enabledCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Disable the SA account and create dedicated named accounts for the administrators — the SA account is a prime target for brute-force attacks. Quick fix, low risk (check beforehand that no application connects with it).
POST004Engine on a supported major versionCritical
Une version majeure hors support ne recoit plus de correctif de securite, y compris pour les failles critiques. Support etendu termine le 2026-07-14 (il y a 67 jours) : plus AUCUN correctif de securite n'est publie pour cette version majeure. (VA1018 / CIS 1.x ; voir aussi UPD004, meme referentiel de dates)
Observed: v13 (13.0.6300.2) SP3
Recommended action: Plan the migration to a supported major version of SQL Server; builds at end of support (SQL 2014 and earlier, SQL 2016 as of 2026-07-14) must be upgraded.
SEC004sysadmin membersHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Bring the list down to 5 members at most and replace the unnecessary sysadmin access with less privileged roles. Inspect the contents of the Windows groups that appear in the list: they count as one member here, but they grant the access to every one of their members.
SEC002Password policyHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Apply the Windows password policy (CHECK_POLICY) to every SQL login — without it, weak or never-expiring passwords weaken authentication. Quick fix, low risk.
SEC003Orphaned usersMedium
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Remap each orphaned user to its server login, or drop it if it is no longer used — an orphan can hide residual access left over from a migration. Moderate effort, low risk.
SEC005Guest account activeMedium
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Revoke the Guest account's access in every user database — an active Guest opens the database to every server login, even an unauthorized one. Quick fix, low risk (do not touch master/tempdb).
SEC006Public role permissionsInfo
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Any permission granted to PUBLIC is granted to every connection, including to a compromised application account. Revoke the server grants beyond the defaults and move them to explicit roles or logins; the CONNECT grants on the built-in TSQL endpoints are normal and present on every instance. The matching verdict is the one carried by PERM014.
SEC023External AI runtimes enabled (external AI runtimes enabled - local ONNX)High
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: If local execution of AI (ONNX) models is not used, have the corresponding server option disabled. Otherwise: allow only models and libraries from verified sources, apply least privilege to embedding generation, strictly restrict the permissions on the models directory and audit the calls.
SURF016CLR strict security enabledHigh
Not applicable on this version: this check requires SQL Server 2017 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2017 or later (instance: SQL Server 2016)
Recommended action: Enable CLR strict security (the .NET components loaded into SQL Server must be signed) and sign the legitimate components.
POST003Trusted assemblies trackedHigh
Not applicable on this version: this check requires SQL Server 2017 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2017 or later (instance: SQL Server 2016)
Recommended action: Document every explicitly approved component (the trusted assemblies list) and have the entries that are not justified removed.
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: If calling external web services from SQL Server is not needed, have the corresponding server option disabled. Otherwise: restrict the right to call external endpoints to the strict minimum, lock down the database-scoped credentials and apply an allowed-URL list or an egress firewall on the host.
SEC024External AI models declared (sys.external_models - outbound data flows)Medium
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: Inventory and justify every declared external AI model (who receives the data). Document the GDPR flow and the processing agreement if personal data leaves the instance. Check that each model uses a dedicated least-privilege credential, and have the unused models removed.
SEC025Server-scoped credentials allowed (allow server scoped db credentials)Medium
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: If the managed identity of the host does not need to be usable at database level, have the server option that allows server-scoped credentials disabled. Otherwise: restrict the authorized accounts and audit the use of the managed identity.
DATA001Sensitive data classification appliedMedium
Not applicable on this version: this check requires SQL Server 2019 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2019 or later (instance: SQL Server 2016)
Recommended action: Run Data Discovery & Classification (SSMS) or ADD SENSITIVITY CLASSIFICATION to label the columns holding personal or sensitive data.
DATA004UNMASK granted narrowlyLow
Not applicable on this version: this check requires SQL Server 2022 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2022 or later (instance: SQL Server 2016)
Recommended action: Revoke the database-wide UNMASK grants and re-grant them at column or schema level only to the roles that strictly need them.
DATA002Likely PII columns not classifiedInfo
Not applicable on this version: this check requires SQL Server 2019 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2019 or later (instance: SQL Server 2016)
Recommended action: Review the flagged columns and apply a sensitivity classification to them, or confirm that they hold no personal data.
DATA008Ledger enabled (integrity required)Info
Not applicable on this version: this check requires SQL Server 2022 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2022 or later (instance: SQL Server 2016)
Recommended action: Create the new databases with LEDGER = ON, or define ledger tables, on the data sets whose integrity must be demonstrable (NIS2/audit requirements).
DATA009Ledger digest verificationInfo
Not applicable on this version: this check requires SQL Server 2022 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2022 or later (instance: SQL Server 2016)
Recommended action: Configure automatic storage of the Ledger digests on immutable media off the server and schedule a regular verification of the database against those digests.
POST001CLR strict security (inventory)Info
Not applicable on this version: this check requires SQL Server 2017 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2017 or later (instance: SQL Server 2016)
Recommended action: See SURF016: a single setting fixes both checks. Enable "clr strict security" and have the legitimate .NET components signed with a certificate or an asymmetric key — an unsigned component can run arbitrary code on the server.
C
Server settingsSettings that drive stability and performance.
4 Gaps · 27 Compliant
CFG001Max Server MemoryCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Cap the maximum server memory, reserving RAM for the OS (starting rule: total RAM - 4 GB, or - 10% above 16 GB) — without a cap, SQL Server can starve the system and cause swapping. Quick intervention, low risk.
CFG004MAXDOPHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: NUMA: min(8, cores/node). Without NUMA: min(8, total cores)
CFG003Cost Threshold for ParallelismMedium
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Raise the cost threshold for parallelism (recommended starting point: 50) — the default of 5 parallelizes too many small queries and wastes CPU on OLTP workloads. Quick intervention, low risk.
CFG002Min Server MemoryLow
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Usually 0 or 25% of max server memory
QOPT006DOP/CE feedback disabled (2022)Info
Not applicable on this version: this check requires SQL Server 2022 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2022 or later (instance: SQL Server 2016)
Recommended action: Enable CE/DOP feedback with Query Store in READ_WRITE for adaptive auto-tuning.
QOPT004PSP optimization disabled (2022)Info
Not applicable on this version: this check requires SQL Server 2022 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2022 or later (instance: SQL Server 2016)
Recommended action: Re-enable PSP except in a documented case; it generates several plans for highly skewed predicates.
F
File layoutHow the database is stored on disk — room to grow.
2 Gaps · 8 Compliant
FILE001Data and Log on the same diskHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Move the log files to a dedicated disk
FILE002TempDB on the system diskHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Move TempDB to a dedicated fast disk (SSD)
B
BackupsYour safety net if data is lost or corrupted.
3 Gaps · 8 Compliant
BACK003Recent log backupCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Schedule log backups every 15-60 minutes depending on RPO
BACK001Recent full backupCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Schedule full backups at least weekly
Routine upkeepHousekeeping that keeps the database fast and reliable.
3 Gaps · 30 Compliant
MAINT001Recent DBCC CHECKDBCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Schedule a weekly integrity check (CHECKDB) on every database — it is the only way to detect silent corruption early, before it spreads to the backups. Moderate effort, low risk.
MAINT002Index fragmentationMedium
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Reorganize (10-30%) or Rebuild (>30%) the indexes
MAINT003Stale statisticsInfo
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Update the statistics regularly (maintenance job) and make sure the automatic statistics update is enabled — stale statistics degrade execution plans. Moderate effort, low risk.
P
SpeedThe responsiveness your users feel day to day.
2 Gaps · 24 Compliant
PERF001Page Life ExpectancyMedium
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Corroborate with the wait stats (PAGEIOLATCH) before concluding that there is memory pressure; check Max Server Memory
PERF002Buffer Cache Hit RatioInfo
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Do not rely on the BCHR; use the wait stats and the PLE trend
TDB005XTP growth (HkTempDB) in TempDBMedium
Not applicable on this version: this check requires SQL Server 2019 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2019 or later (instance: SQL Server 2016)
Recommended action: Review the heavy use of memory-optimized temporary objects; significant growth can exhaust memory.
TDB003Memory-optimized TempDB metadataInfo
Not applicable on this version: this check requires SQL Server 2019 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2019 or later (instance: SQL Server 2016)
Recommended action: On workloads with heavy contention on the tempdb temporary database, have memory-optimized tempdb metadata enabled (an instance restart is required).
PERF009Optimized locking not enabled (SQL Server 2025 - recommendation)Info
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: On the eligible databases, after validation in pre-production (application locking hints may be affected), have Accelerated Database Recovery enabled and then optimized locking. Also enable Read Committed Snapshot Isolation to get the maximum benefit.
R
Service continuityStaying available and recovering after an incident.
3 Gaps · 59 Compliant
REL001Corruption detectedCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Run a full integrity check of the database, determine the extent of the corruption, then restore the pages or the database from a healthy backup — untreated corruption leads to data loss. Urgent action, high risk (get expert assistance before attempting any repair).
REL002Memory dumpsHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Analyze the dumps and contact Microsoft support if they recur
REL003Mirroring statusInfo
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Resolve the synchronization problems
Not applicable on this version: this check requires SQL Server 2017 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2017 or later (instance: SQL Server 2016)
Recommended action: A value that is too high blocks all writes if a secondary goes down. Align RSSTC with the actual number of synchronous secondaries and with your fault tolerance.
AG027Contained availability group system databasesMedium
Not applicable on this version: this check requires SQL Server 2022 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2022 or later (instance: SQL Server 2016)
Recommended action: A contained AG without its contained system databases does not fail over logins, jobs and configuration. Recreate the AG including the contained system databases.
U
UpdatesSecurity and stability patches applied to the engine.
1 Gaps
UPD004End of supportCritical
Fin du support ETENDU Microsoft pour cette version majeure. Passe cette date, plus aucun correctif de securite n'est publie. Le support courant (mainstream) se termine plusieurs annees plus tot : passe cette date, plus de correctif fonctionnel. Meme referentiel de dates que POST004. Extended Security Updates (ESU) : un programme payant de correctifs de securite reste ouvert jusqu'au 2029-07-17 (editions Enterprise et Standard, dernier Service Pack requis). Le collecteur ne peut pas voir si l'instance y est inscrite : un ESU retarde l'echeance, il ne remplace pas la migration.
Observed: 2026-07-14 (OUT OF SUPPORT for 67 days)
Recommended action: Plan a migration to a supported version
I
Disk accessRead/write speed on the underlying storage.
Recommended action: Move hot files to faster storage and spread the I/O load.
DB
Database healthSettings at the level of each individual database.
DBLVL007Native JSON data type inventory (SQL Server 2025)Info
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: No fix — governance inventory. Note the correlation with preview features (the native JSON type is in preview on SQL Server 2025 on-prem). Have the JSON indexing strategy and the retention of this data validated.
DBLVL006VECTOR data type inventory (SQL Server 2025)Info
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: No fix — governance inventory. Check: backup sizing (large embeddings), data classification (embeddings derived from personal data => GDPR), encryption at rest (TDE) of the databases concerned.
QS
Performance historyThe history used to diagnose slowdowns.
QS007QS Wait Stats captureInfo
Not applicable on this version: this check requires SQL Server 2017 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2017 or later (instance: SQL Server 2016)
Recommended action: Enable wait statistics capture in Query Store (SQL 2017+) — it links each query to its wait types and speeds up diagnosis. Quick to do, low risk.
DS
Database optionsPer-database settings affecting security and speed.
3 Gaps · 8 Compliant
DBSET003Page Verify not CHECKSUMCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Set the page verification option to CHECKSUM on each database — this is what allows silent disk corruption to be detected. Quick to do, low risk (protection only covers pages written after the change).
DBSET002AutoShrink enabledHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Turn off AutoShrink on each affected database — repeated automatic shrinks cause massive index fragmentation and needless I/O load. Quick to do, low risk.
DBSET001AutoClose enabledHigh
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Turn off AutoClose on each affected database — it closes the database on every disconnect and forces a costly reopen on the next connection. Quick to do, low risk.
DBSET010PREVIEW_FEATURES enabled on a database (SQL Server 2025)High
Not applicable on this version: this check requires SQL Server 2025 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2025 or later (instance: SQL Server 2016)
Recommended action: On production databases, after dropping or rebuilding any persistent object produced by a preview feature (vector index, JSON index), have preview features disabled. Reserve them for development and test environments.
Not applicable on this version: this check requires SQL Server 2019 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2019 or later (instance: SQL Server 2016)
Recommended action: On the transactional databases affected by long transactions or by log growth tied to active transactions, have accelerated database recovery (ADR) enabled during a quiet window (an exclusive lock is required). Then monitor the size of the version store and plan the disk space required. Avoid long transactions and large structure changes in a single transaction.
En
Data encryptionWhether your data stays unreadable if a disk is stolen.
2 Gaps · 11 Compliant
ENC002TDE certificates backupCritical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Back up each TDE certificate together with its private key and keep them off-server in a secure vault — without this backup, an encrypted database becomes unrecoverable after a disaster. Quick to do, low risk (be sure to protect the key password).
ENC001TDE status detailsInfo
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Informational: current TDE encryption state
DATA007Always Encrypted enclave/attestationInfo
Not applicable on this version: this check requires SQL Server 2019 or later, and this instance runs SQL Server 2016 (13.0.6300.2). The check is left out of the score; it is not a finding.
Observed: Not applicable: requires SQL Server 2019 or later (instance: SQL Server 2016)
Recommended action: Configure an enclave type (column encryption enclave type) and an attestation service (HGS) when in-place operations on encrypted columns are required.
SQL Audit PlatformSRV-APP-01
Checks not applicable and not evaluated
Neither gaps nor passes: a not-applicable check does not exist on this version or edition, or examines a feature the instance does not use; a not-evaluated check could not be read (rights, network, missing data).