Database Settings
The 13 checks in the “Database Settings” category of a SQL Server audit: what each one verifies, its severity and the versions covered.
- Checks in this category
- 13
- Weight in the score
- 12
- Breakdown by severity
- 1 critical · 4 high · 5 medium · 1 low · 2 info
Checks in this category
DBSET003Page Verify Not CHECKSUM
CriticalVerifies that PAGE_VERIFY is set to CHECKSUM for each database
Versions : 2012-2025
DBSET001AutoClose Enabled
HighDetects databases with AUTO_CLOSE enabled, which degrades performance
Versions : 2012-2025
DBSET002AutoShrink Enabled
HighDetects databases with AUTO_SHRINK enabled, which causes fragmentation
Versions : 2012-2025
DBSET010PREVIEW_FEATURES enabled on a database (SQL Server 2025)
HighFlags user databases (and the model template) where the PREVIEW_FEATURES database-scoped configuration is ON. Microsoft explicitly recommends preview features for dev/test only, not production; persisted preview objects (vector/JSON indexes) can block disabling it later.
Versions : 2025
DBSET012Delayed Durability FORCED (risk of committed-data loss)
HighInspects database-level transaction durability via sys.databases.delayed_durability_desc (DISABLED | ALLOWED | FORCED, SQL 2014+). FORCED makes every commit asynchronous: control returns to the client before the log record is hardened. On crash, shutdown/restart or failover, all committed-but-unflushed transactions are silently lost. ALLOWED only permits per-transaction opt-in (risk only if the application requests it).
Versions : 2014-2025
DBSET004Compatibility Level vs Engine
MediumCompares each database compatibility level with the SQL engine version
Versions : 2012-2025
DBSET007Auto Update Statistics OFF
MediumDetects databases with AUTO_UPDATE_STATISTICS disabled
Versions : 2012-2025
DBSET008Auto Create Statistics OFF
MediumDetects databases with AUTO_CREATE_STATISTICS disabled
Versions : 2012-2025
DBSET009Database collation mismatch
MediumCompares each database collation against tempdb and the server. A mismatch raises collation-conflict errors as soon as a query joins a user table to a temp table.
Versions : 2012-2025
DBSET013Change Tracking auto-cleanup / retention hygiene
MediumFor every Change-Tracking-enabled database (sys.change_tracking_databases) checks auto-cleanup (is_auto_cleanup_on) and retention (retention_period + retention_period_units). Auto-cleanup OFF means the internal side tables (change_tracking_* prefix) and syscommittab are never purged: unbounded internal growth, storage bloat and degrading CHANGETABLE. Excessively long retention causes the same effect more slowly. Default retention is 2 days.
Versions : 2012-2025
DBSET011Accelerated Database Recovery (ADR) disabled
LowReports Accelerated Database Recovery state per online user database (sys.databases.is_accelerated_database_recovery_on, SQL Server 2019+). ADR redesigns crash recovery via a persistent version store, SLOG and logical revert, giving near-instant rollback, aggressive log truncation and constant-time recovery. Advisory check: lists ADR-off databases and escalates only when an ADR-off database currently shows the exact pain ADR relieves (log held by an active transaction).
Versions : 2019-2025
DBSET005RCSI (Read Committed Snapshot)
InfoChecks if Read Committed Snapshot Isolation (RCSI) is enabled on databases
Versions : 2012-2025
DBSET006CDC (Change Data Capture)
InfoIdentifies databases with Change Data Capture (CDC) enabled
Versions : 2012-2025
Other categories
- Security 103
- Backups 11
- Reliability 64
- Encryption 14
- Configuration 33
- Maintenance 33
- Performance 29
- Files 10
- Wait Statistics 9
- Advanced I/O 5
- Advanced Memory 8
- Blocking & Deadlocks 8
- Agent 8
- Query Store 8
- Linked Servers 5
- Capacity 9
- Updates 7
- Hardware 10
- Top Queries 7
- Stored Procedures 4
- Connections 6
- Extended Events 4
- Database Mail 3
- Database Level 7