DaysToSplitDatabaseOn - System Parameter
DaysToSplitDatabaseOn sets the maximum age, in days since it was created, of the online Log Database. When the online Log Database is older than this, the Logging Service creates a new online Log Database, and the previous one becomes an archive Log Database.
At a Glance
| Property | Value |
|---|---|
| Key | DaysToSplitDatabaseOn |
| Data type | integer (days) |
| Default | 10000 (practically disabled) |
| Read by | Logging Service |
| Takes effect | Within about 15 seconds; no restart needed. Applies the next time the Logging Service checks the online Log Database. |
| Status | ✅ Active |
| Since | Nodinite 3 |
How It Works
The Logging Service splits the online Log Database on size (SizeToSplitDatabaseOn) or age (this parameter), whichever limit is reached first. The default of 10000 days (more than 27 years) means age never triggers a split in practice, so the size limit decides.
When the limit is reached, the Logging Service creates the new Log Database from the related System Parameters (name, file placement, recovery model, access, Always On backup); see How a new Log Database is created.
Choosing a Value
- Keep the default unless you want time-based Log Databases. Most installations split on size only.
- Set a value such as
365to start a new Log Database about once a year, for example to plan disk space, backups, or setting older Log Databases to read-only. - The size limit still applies; a busy year can produce more than one Log Database.
Frequently Asked Questions
Can I create Log Databases in advance with planned periods?
Yes. Nodinite ships the Log Database as a DACPAC package; follow Create new Log Databases manually and name the databases per LogDatabaseName.