- 5 minutes to read

Log Databases overview

Keep full control of where your logged data lives. The Log Databases page in the Nodinite Web Client lists every online and archive Log Database, shows its schema version and state, and is where an administrator registers, edits, updates, and removes them.

  • ✅ One list of all Log Databases, with status, schema version, server, and date range
  • ✅ Add, edit, or delete registrations without touching the physical SQL Server databases
  • ✅ Read-only mode for archive Log Databases, for compliance and safe archiving
  • ✅ A guided Update Guide for schema updates after a Nodinite upgrade

The Log Databases list with the online Log Database and two archives, its Version arrow and Remote Server flag, then filtered on 2023, animated walkthrough (7.12)
Animated walkthrough: one online Log Database, the archives behind it, and the filter.

  1. Open Administration > Settings > Log Databases.
  2. The online Log Database has no End Date: it receives the new events.
  3. An archive has a Start Date and an End Date, here also Read Only. Log Views still search it.
  4. A green arrow in Version means its schema is older than the one shipped; see Update Log Database. Remote Server shows whether it is reached through a linked server.
  5. Type part of a name, such as 2023, in the filter box. Only the matching Log Databases are left.

Nodinite stores every Log Event and message received by the Log API or picked up by Log Agents in SQL Server databases called Log Databases. This page covers the administrative side: the list in the Web Client and what you can do with it. For the architecture (how Log Databases split on size or age, how they are named, recovery models, Always On), read What is a Log Database?.

Understanding Log Database administration

The Configuration Database keeps one registration per Log Database: its name, server, active date range, and read-only flag. The Logging Service writes new data to the single online Log Database (the one without an End Date) and creates the next one automatically, governed by System Parameters. Archive Log Databases keep older data and are still searched from Log Views. The Web Client page edits the registrations, never the physical databases.

graph LR Admin["fa:fa-user-gear Administrator
Web Client"] -->|"add, edit, delete,
Update Guide"| Reg["fa:fa-database Configuration Database
Log Database registrations"] Params["fa:fa-sliders System Parameters
split, naming, retention"] -->|"govern"| LS["fa:fa-hard-drive Logging Service"] Reg --> LS LS -->|"writes new events"| Online["fa:fa-database Online Log Database
no End Date"] LS -->|"creates on size or age"| Online Online -->|"becomes archive
when the next is created"| Archive["fa:fa-box-archive Archive Log Databases
optionally read-only"] Views["fa:fa-magnifying-glass Log Views"] -->|"search"| Online Views -->|"search"| Archive style Admin fill:#2678BD,color:#fff style Reg fill:#3F827B,color:#fff style Params fill:#9E59BB,color:#fff style LS fill:#E47528,color:#fff style Online fill:#93d16d,color:#000 style Archive fill:#3F827B,color:#fff style Views fill:#2678BD,color:#fff

Blue: where people work (Web Client, Log Views). Purple: the System Parameters that govern the Logging Service (orange). Green: the online Log Database receiving new data. Teal: the registrations and archive Log Databases.

The Log Databases list

Column Meaning
(no header) A database icon with a green check (Online) or a red cross (Offline, the Log Database is not available right now)
Database The name of the Log Database, by default following the LogDatabaseName pattern
Version The schema version, compared with the Nodinite.LogDatabase.dacpac file on the Web API server: a green arrow means older (update available, see Update Log Database), a yellow arrow newer (a preview or test build), a check the same
Server The Linked Server / Listener Name of the SQL Server (localhost when it is on the same instance as the Configuration Database)
Description A user-friendly description (room for comments)
Start Date / End Date The period of logged records; the online Log Database has no End Date, and only one Log Database may lack one
Read Only ✅ Read-only: no maintenance, inserts, or deletes; ❌ Writable
Remote Server ✅ Remote: the Log Database is reached through a Linked Server; ❌ Same instance

Log Databases page with Update Guide and Add Log Database, the filter, and the online Log Database and two archives (7.12)
The Log Databases list shows the schema version, server, date range, and the read-only and remote flags for each database.

Click a column header to sort; every column except Version sorts. A Log View search uses every available Log Database whose Start and End Date overlap its time range, online and archive alike. An Offline Log Database is skipped without a warning, so its events are simply missing from the result.

Filter

Enter text in the filter box to narrow down the list. The list has no Include deleted, Tags, or With Selected: a Log Database registration is removed with Delete on its edit page.

Operations

An administrator can Add a Log Database registration, for example to bring back a moved archive.

Add Log Database button on the Log Databases page (7.12)
The button opens the form for registering a new or moved Log Database.

An administrator can Edit a record by clicking its name or by selecting Edit, the only entry, from the Action menu. The page, the edit page, and the Update Guide need the Administrators Role.

Action menu of a Log Database with its one entry, Edit (7.12)
Edit a registration to change its server after a move, its description, or its read-only flag.

An administrator can Update the database schema using the Update Guide wizard. New 7.2.0

Important

Review the Update Guide after every Nodinite upgrade to make sure all Log Databases run the latest schema version. The Update Guide stops and restarts the services, sets archive databases read-only, and generates the SqlPackage.exe scripts for you.

System Parameters that govern Log Databases

These System Parameters control how the Logging Service creates, names, maintains, and cleans up Log Databases. The full table, with how each one is used when a new Log Database is created, is in System Parameters for Log Databases.

Area System Parameters
When a new Log Database is created SizeToSplitDatabaseOn (in GB), DaysToSplitDatabaseOn
Name, files, and recovery model LogDatabaseName, EnvironmentName, LogLocations, LogDatabaseRecovery
SQL Server and deployment SqlServer, SqlPackageExecutable, SqlPackageParams, AvailabilityGroupBackupPath
Access LogServiceUsers, LogAccessRoles
Maintenance and cleanup DatabaseMaintenance, CleanUpTimerInterval
Retention of logged data DaysToKeepMessageEventsDefault, DaysToKeepMessageDataDefault, DaysToKeepMessageContextDefault, DaysToKeepErrorEventsWithoutData, DaysToKeepLogAudits

Next Steps