Add or manage a Nodinite Log Database
Add, manage, move, and delete Log Database registrations in Nodinite to keep log data storage secure, efficient, and scalable. This guide helps administrators configure SQL Server settings, use cheaper storage for old data, and stay compliant.
- ✅ Add, edit, move, and delete Log Databases without touching physical SQL data
- ✅ Flexible configuration for SQL Server, Always-On, and linked servers
- ✅ Read-only mode for compliance and safe archiving
- ✅ Administration from the Web Client
The registration tells Nodinite where each physical Log Database is. You don't touch the physical database within the Microsoft SQL Server instance in any way when you add or remove a registration from within the Nodinite Web Client. The physical database is created by the Nodinite Logging Service (governed by SizeToSplitDatabaseOn and DaysToSplitDatabaseOn) or by creating it manually.
Use the administration pages in the Web Client to:
- Change the location information after moving a database from one SQL Server instance to another, for example to a SQL Server hotel where disk is cheaper, or to use hardware resources better. Renaming a Log Database is also possible.
- Register an archive Log Database that was moved or restored.
- Set an archive Log Database read-only.
- Safely delete empty archive databases.
Tip
Updating database schemas: when Nodinite releases a new version with schema improvements, use the Update Log Database wizard. It handles service pauses, recovery models, and DACPAC deployment. Don't apply schema changes manually.
Understanding the Log Database lifecycle
Each Log Database moves through the same stages. The Web Client registration follows it all the way, and only the last step happens outside Nodinite.
Logging Service or manually"] --> B["fa:fa-database Online
receives new events, no End Date"] B -->|"next Log Database created"| C["fa:fa-box-archive Archive
searched from Log Views"] C -->|"optional"| D["fa:fa-lock Read-only
no maintenance or deletes"] C -->|"retention empties it"| E["fa:fa-trash-can Empty
delete the registration"] D --> E E -->|"SSMS"| F["fa:fa-ban Physical database dropped"] style A fill:#2678BD,color:#fff style B fill:#93d16d,color:#000 style C fill:#3F827B,color:#fff style D fill:#9E59BB,color:#fff style E fill:#FFD525,color:#000 style F fill:#c33d34,color:#fff
Green: the single online Log Database. Teal and purple: archive and read-only archive databases. Yellow: empty, ready for removal. Red: the irreversible drop, done in SQL Server Management Studio.
How fast an archive Log Database empties depends on the retention System Parameters, for example DaysToKeepMessageEventsDefault and DaysToKeepMessageDataDefault, applied by the Logging Service cleanup every CleanUpTimerInterval.
Instructions
A name for the Log Database is mandatory. To insert new Log Events, Nodinite must always know about at least one Log Database.
The Add Log Database page and the edit page have these fields:
- Database (the name)
- Linked Server / Listener Name (might include the instance name)
- Remote server
- Read-only
- Archive Database (on Add only)
- Start date-time and End date-time
- Description

Add Log Database is a page, not a dialog. Fields marked with one star are required; fields marked with two stars can only be changed after the End date has passed.
Register a restored archive

Animated walkthrough: the dates come from the database itself.
- On the Log Databases page, click Add Log Database.
- Enter Database, here Nodinite_DEV_Log_20221228, and Linked Server / Listener Name, here
localhost. - Archive Database is ticked by default, so the date fields are hidden. Tick Read-only and add a Description.
- Click Save and close. The list shows the registration with the Start and End Date of its events.
Edit a registration

Animated walkthrough: only the registration changes, never the database itself.
- Click the name of the Log Database in the list, or choose Edit from its Action menu.
- Change what you need, here the Description. Start date-time and End date-time are read-only once saved.
- Click Save and close. The list shows the change.
Database
Enter the database name. This field is required to create the Log Database configuration.
The name follows the LogDatabaseName pattern, by default Nodinite_<EnvironmentName>_Log_{year}{month}{day}, for example Nodinite_Prod_Log_20251028. Databases upgraded from older versions keep their original names. See Log Database Naming for how the pattern is built from EnvironmentName. New 7.12 The hint under Database explains the pattern: {year}, {month}, and {day} are replaced by the start date, so Nodinite_DEV_Log_{year}{month}{day} gives Nodinite_DEV_Log_20241113; use the same pattern for a database you add by hand.

The Database hint, and the End date-time hint saying the active Log Database can't be deleted.
Linked Server / Listener Name
Add the name of the target SQL Server instance. The database must exist on that server, and the pair of Database and Linked Server / Listener Name must be unique.
- If the Log Database is located on the same server as the Nodinite Configuration Database, use
localhostorlocalhost\instancename. - Otherwise, enter the name of the linked server. Remote Log Databases are always accessed through linked servers. The SqlServer System Parameter holds the linked server name Nodinite uses for Log Databases.
Read-Only
Check this checkbox to make the Log Database read-only. When checked, there is no internal maintenance (see DatabaseMaintenance), and operations like re-index, delete/truncate, or insert are suspended. Nodinite still searches the database from Log Views.
Note
The Read-Only flag can only be checked for an archive Log Database: on Add, Archive Database must be ticked, and on edit, its End date must have passed. The online Log Database can never be read-only.
Remote Server
In relation to the Nodinite Configuration Database, check the checkbox if the Log Database is located on a remote SQL Server instance.
Remote Log Databases require a linked server between the SQL Server instance with the Configuration Database and the remote Log Database.
Archive Database
Archive Database is ticked by default on Add. Keep it ticked when you register an older Log Database, for example one you moved or restored: the date fields are hidden, and Nodinite sets the start and end time from the oldest and newest Log Event, Log Audit, or Monitor Event in it. A database without data is refused (The database contains no data and should not be added).
Untick it to register a future Log Database with a Start date-time, for example one you created manually. That sets the End Date of the current online Log Database to the new Start date-time, so the new one becomes the online Log Database. Only one Log Database can lack an End Date.
Start date-time
For an archive Log Database, this is the start date for Log Events. For a future Log Database (for example one you created manually), this value makes sure future events enter the correct target database when the time comes.

Both dates are read-only once the registration is saved. The End date-time is set from the Start date of the next Log Database, or left empty for the online one.
End date-time
For an archive Log Database, this is the end date for Log Events in that particular database. Nodinite sets it from the Start date of the next Log Database.
The topmost (last or current) Log Database is not allowed to have an end date.
Description
The optional field Description gives this configuration a user-friendly meaning.
Delete Log Database
As time goes by, the archive Nodinite Log Databases get smaller and smaller as retention removes old data, until they are empty. The Nodinite administrator can and should remove empty Log Databases. Deleting a non-empty Log Database results in permanent, irreversible data loss: the data is no longer accessible from the Nodinite Web Client or the Web API.
Tip
If you manage multiple environments or delete databases on a recurring basis, use the automated SQL Server Agent job instead of deleting manually here. It is repeatable, respects your retention policy, and removes the risk of human error.
The current (online) Log Database, the one without an end date, cannot be deleted: New 7.12 its edit page has no Delete button, and the Web API refuses the delete (HTTP 400, … is the online Log Database and cannot be deleted). The physical database is not deleted in SQL Server; you must delete it manually from within SSMS.
To manually remove an empty archive Log Database, follow the steps below in order. Skipping steps or reversing the order can leave your system in an inconsistent state.
Important
Dropping a database is permanent and irreversible: there is no undo, no recycle bin, and no way to recover the data afterwards. Always verify the database is empty and that your retention policy permits removal before proceeding.

Animated walkthrough: the registration goes, the database stays on the SQL Server.
- Make sure the database is empty. Use SSMS, or open the Log Database and click Show Database Report (optional): it shows the size, the event counts, and the backups.

The database report shows how much data is left in the Log Database. - Click Delete in the footer of the edit page.

An archive Log Database (here the first half of 2024) has Delete in its footer.

The online Log Database has no Delete button.
Confirm intent to Delete asks you to confirm, under a WARNING - POSSIBLE DATA LOSS banner. Click Yes. The page confirms the deletion and returns to the list.

The dialog states that the physical database in SQL Server is not deleted. - Remove the physical database from the SQL Server instance using SSMS (not from the file system directly). This frees disk space on SQL Server. Deleting the files directly bypasses SQL Server's shutdown procedures and can corrupt system metadata.
Always-On
If you use a SQL Server Always-On availability group to host the Log Database, provide the following details:
- Enter the name of the Always-On group (usually the listener name) as Linked Server / Listener Name.
- Check Remote server.

Example settings for a SQL Server Always-On availability group.
Make sure the linked servers are set up using the listener name. Review the 'About Always-On' user guide for details.
For new Log Databases in an availability group, set LogDatabaseRecovery to FULL and AvailabilityGroupBackupPath to the network share the Logging Service uses for the backup that the secondary replicas restore.
Troubleshooting
The following user guides are usually helpful:
How do I move a Nodinite Log Database?
Moving a Nodinite Log Database is detailed in the 'Moving Nodinite Databases' user guide. After the move, edit the registration here and change Linked Server / Listener Name (and Remote server) accordingly.