SQL Audit Platform
SQL Server audit report
Prepared for

SRV-APP-01

production Microsoft SQL Server 2016 (SP3) Standard Edition (64-bit) srv-app-01.atlantique.local
47
Global health score
Critical F
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 on 18 September 2026
Document generated on 25 September 2026
Collector 4.12.0
SQL Audit Platform SRV-APP-01

Executive summary

25 check(s) not applicable to SQL Server 2016 — Details at the end of the report.

47
Global health score
Critical F
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 attack Critical

In case of disk failure, corruption or ransomware, you risk losing data with no way to restore it.

Risk level Critical Effort High
Recommended action Schedule log backups every 15-60 minutes depending on RPO
2
Your database is exposed to unauthorized access Critical

A security gap can allow theft or leakage of your customer and business data.

Risk level Critical Effort 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 recovery Critical

If your service continuity isn't guaranteed, an outage can halt your operations for hours or days.

Risk level Critical Effort 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 practices Critical

Unsuitable settings can undermine the stability, security or performance of your database.

Risk level Critical Effort 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 encrypted Critical

If files or media are stolen, the data stays readable and GDPR compliance is not ensured.

Risk level Critical Effort 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 place Critical

Without maintenance, data issues go unnoticed and worsen over time.

Risk level Critical Effort 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 Platform SRV-APP-01

Technical annex — detailed results

Detailed gaps and warnings by domain, with the recommended remediation guidance.

S
Access security Who can reach the database and what they may do there.
6 Gaps · 1 Warnings · 84 Compliant
SEC001 SA account enabled Critical
É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).
POST004 Engine on a supported major version Critical
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.
SEC004 sysadmin members High
É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.
SEC002 Password policy High
É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.
SEC003 Orphaned users Medium
É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.
SEC005 Guest account active Medium
É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).
SEC006 Public role permissions Info
É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.
SEC023 External 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.
SURF016 CLR strict security enabled High
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.
POST003 Trusted assemblies tracked High
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.
SEC022 External REST invocation enabled (external rest endpoint enabled) 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 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.
SEC024 External 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.
SEC025 Server-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.
DATA001 Sensitive data classification applied Medium
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.
DATA004 UNMASK granted narrowly Low
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.
DATA002 Likely PII columns not classified Info
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.
DATA008 Ledger 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).
DATA009 Ledger digest verification 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: Configure automatic storage of the Ledger digests on immutable media off the server and schedule a regular verification of the database against those digests.
POST001 CLR 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 settings Settings that drive stability and performance.
4 Gaps · 27 Compliant
CFG001 Max Server Memory Critical
É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.
CFG004 MAXDOP High
Écart détecté — voir remédiation.
Observed: KO
Recommended action: NUMA: min(8, cores/node). Without NUMA: min(8, total cores)
CFG003 Cost Threshold for Parallelism Medium
É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.
CFG002 Min Server Memory Low
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Usually 0 or 25% of max server memory
QOPT006 DOP/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.
QOPT004 PSP 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 layout How the database is stored on disk — room to grow.
2 Gaps · 8 Compliant
FILE001 Data and Log on the same disk High
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Move the log files to a dedicated disk
FILE002 TempDB on the system disk High
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Move TempDB to a dedicated fast disk (SSD)
B
Backups Your safety net if data is lost or corrupted.
3 Gaps · 8 Compliant
BACK003 Recent log backup Critical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Schedule log backups every 15-60 minutes depending on RPO
BACK001 Recent full backup Critical
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Schedule full backups at least weekly
BACK002 Differential backup configured Info
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Schedule daily differential backups
M
Routine upkeep Housekeeping that keeps the database fast and reliable.
3 Gaps · 30 Compliant
MAINT001 Recent DBCC CHECKDB Critical
É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.
MAINT002 Index fragmentation Medium
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Reorganize (10-30%) or Rebuild (>30%) the indexes
MAINT003 Stale statistics Info
É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
Speed The responsiveness your users feel day to day.
2 Gaps · 24 Compliant
PERF001 Page Life Expectancy Medium
É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
PERF002 Buffer Cache Hit Ratio Info
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Do not rely on the BCHR; use the wait stats and the PLE trend
TDB005 XTP growth (HkTempDB) in TempDB Medium
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.
TDB003 Memory-optimized TempDB metadata Info
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).
PERF009 Optimized 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 continuity Staying available and recovering after an incident.
3 Gaps · 59 Compliant
REL001 Corruption detected Critical
É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).
REL002 Memory dumps High
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Analyze the dumps and contact Microsoft support if they recur
REL003 Mirroring status Info
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Resolve the synchronization problems
AG012 REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT misconfigured High
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.
AG027 Contained availability group system databases Medium
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
Updates Security and stability patches applied to the engine.
1 Gaps
UPD004 End of support Critical
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 access Read/write speed on the underlying storage.
2 Gaps · 3 Compliant
IO001 Latency per disk High
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Above ~20 ms, investigate the storage (queue, cache, contention, sizing).
IO002 Slowest files Medium
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Move hot files to faster storage and spread the I/O load.
DB
Database health Settings at the level of each individual database.
DBLVL007 Native 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.
DBLVL006 VECTOR 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 history The history used to diagnose slowdowns.
QS007 QS Wait Stats capture 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: 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 options Per-database settings affecting security and speed.
3 Gaps · 8 Compliant
DBSET003 Page Verify not CHECKSUM Critical
É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).
DBSET002 AutoShrink enabled High
É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.
DBSET001 AutoClose enabled High
É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.
DBSET010 PREVIEW_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.
DBSET011 Accelerated Database Recovery (ADR) disabled Low
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 encryption Whether your data stays unreadable if a disk is stolen.
2 Gaps · 11 Compliant
ENC002 TDE certificates backup Critical
É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).
ENC001 TDE status details Info
Écart détecté — voir remédiation.
Observed: KO
Recommended action: Informational: current TDE encryption state
DATA007 Always Encrypted enclave/attestation Info
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 Platform SRV-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).

Not applicable to SQL Server 2016 (25)

CheckTitleReason
AG012REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT misconfiguredSQL Server version
AG027Contained availability group system databasesSQL Server version
DATA001Sensitive data classification appliedSQL Server version
DATA002Likely PII columns not classifiedSQL Server version
DATA004UNMASK granted narrowlySQL Server version
DATA007Always Encrypted enclave/attestationSQL Server version
DATA008Ledger enabled (integrity required)SQL Server version
DATA009Ledger digest verificationSQL Server version
DBLVL006VECTOR data type inventory (SQL Server 2025)SQL Server version
DBLVL007Native JSON data type inventory (SQL Server 2025)SQL Server version
DBSET010PREVIEW_FEATURES enabled on a database (SQL Server 2025)SQL Server version
DBSET011Accelerated Database Recovery (ADR) disabledSQL Server version
PERF009Optimized locking not enabled (SQL Server 2025 - recommendation)SQL Server version
POST001CLR strict security (inventory)SQL Server version
POST003Trusted assemblies trackedSQL Server version
QOPT004PSP optimization disabled (2022)SQL Server version
QOPT006DOP/CE feedback disabled (2022)SQL Server version
QS007QS Wait Stats captureSQL Server version
SEC022External REST invocation enabled (external rest endpoint enabled)SQL Server version
SEC023External AI runtimes enabled (external AI runtimes enabled - local ONNX)SQL Server version
SEC024External AI models declared (sys.external_models - outbound data flows)SQL Server version
SEC025Server-scoped credentials allowed (allow server scoped db credentials)SQL Server version
SURF016CLR strict security enabledSQL Server version
TDB003Memory-optimized TempDB metadataSQL Server version
TDB005XTP growth (HkTempDB) in TempDBSQL Server version