- 2 minutes to read

LogDatabaseName - System Parameter

LogDatabaseName sets the naming pattern the Logging Service uses when it creates a new Log Database. It is one of the System Parameters applied in How a new Log Database is created.

At a Glance

Property Value
Key LogDatabaseName
Data type string
Default Set by the installer: Nodinite_<EnvironmentName>_Log_{year}{month}{day}
Read by Logging Service
Takes effect Within about 15 seconds; no restart needed. Applies to the next Log Database the Logging Service creates.
Status ✅ Active

How It Works

When the online Log Database reaches SizeToSplitDatabaseOn or DaysToSplitDatabaseOn, the Logging Service builds the name of the new Log Database from this pattern. Existing Log Databases keep their names; changing the pattern affects only Log Databases created afterwards.

LogDatabaseName System Parameter in the Web Client (7.x)
The installer has written the environment name DEV into the pattern; the date placeholders remain.

Value Format

The value is plain text with three placeholders, which the Logging Service replaces with the creation date of the new Log Database:

Placeholder Replaced with Example
{year} Year 2025
{month} Month 10
{day} Day 28

The installer writes your EnvironmentName into the value as plain text. Documentation writes this part as %environmentname%, for example Nodinite_%environmentname%_Log_{year}{month}{day}; it is not a placeholder the Logging Service replaces.

Installation Pattern Example name
Nodinite 7 Nodinite_<EnvironmentName>_Log_{year}{month}{day} Nodinite_Prod_Log_20251028
Before Nodinite 7 NodiniteLog_<EnvironmentName>_{year}{month}{day} NodiniteLog_Prod_20251028

Log Databases created before an upgrade keep their old names; see Log Databases.

Choosing a Value

  • Keep the installer's value unless you have a naming standard to follow.
  • Include the environment name, so several Nodinite environments can share one SQL Server instance without name conflicts.
  • Keep the date placeholders, so every new Log Database gets a unique name.
  • Keep the Nodinite prefix if your DBA excludes Nodinite databases from other maintenance jobs by name (see DatabaseMaintenance).
  • SQL Server database naming rules apply; letters, digits, hyphens, and underscores are safe.
  • When you create Log Databases manually, name them with the same pattern.

Next Steps