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

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.

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

The Log Databases list shows the schema version, server, date range, and the read-only and remote flags for each database.

Filter

Enter text in the filter text box to narrow down a large number of records in the list.

Operations

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

The button opens the form for registering a new or moved Log Database.

An administrator can Edit a record by clicking on it or by selecting Edit from the Action button menu.

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.

Note

MaintenanceMode is a Web API flag; it doesn't pause the Logging Service or the Monitoring Service. Use the Stop Services step in the Update Guide instead.

Next Steps

• Add or manage Log Database
• Update Log Database
• Manage System Parameters

Related Topics

• What is a Log Database?
• System Parameters for Log Databases
• Create new Log Databases Manually
• Update Log Databases (Core Services)
• Log Databases troubleshooting
• Automating removal of old Log Databases
• Moving Nodinite Databases
• Configuration Database
• Logging Service
• Core Services
• System Parameters
• Settings overview
• Administration in the Web Client