- 2 minutes to read
LogDatabaseRecovery - System Parameter
LogDatabaseRecovery sets the SQL Server recovery model, SIMPLE or FULL, that the Logging Service gives each new Log Database. The Log Database Update Guide also uses it when it generates update scripts. It is one of the System Parameters applied in How a new Log Database is created.
At a Glance
| Property | Value |
|---|---|
| Key | LogDatabaseRecovery |
| Data type | string (SIMPLE or FULL) |
| Default | SIMPLE; the installer sets FULL for Always On Availability Groups |
| Read by | Logging Service; the Update Guide for Log Databases |
| Takes effect | Within about 15 seconds; no restart needed. Applies to the next Log Database the Logging Service creates and the next update script. |
| Status | ✅ Active |
How It Works
The CLI-based Nodinite installer sets the value from your SQL Server environment:
| SQL Server environment | Value |
|---|---|
| Always On Availability Group (AOAG) | FULL |
| Standalone, including failover cluster | SIMPLE |
- The Logging Service creates every new Log Database with this recovery model.
- The Update Guide includes the matching recovery setting in the scripts it generates for existing Log Databases.
Important
Changing the value does not change the recovery model of existing Log Databases.
Choosing a Value
- Use
FULLwhen the Log Databases are in an Always On Availability Group; databases in an availability group must use the full recovery model. Also set AvailabilityGroupBackupPath. - Use
SIMPLEon a standalone instance or a failover cluster, unless your backup policy needs point-in-time restore. - With
FULL, your DBA must schedule transaction log backups, or the transaction log keeps growing. LogLocations decides which disk holds it. - If an existing Log Database uses a different recovery model than this value, change the value before you retrieve an update script; see Update Log Database.