- 7 minutes to read

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.

graph LR A["fa:fa-plus Created
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 following fields exist for a Log Database:

  • Database (name)
  • Server (might include the instance name)
  • Whether the database is located on a remote server
  • Read Only
  • Archive Database
  • Start date and End date
  • Description

Add Log Database form with Database, Server, remote server, Read Only, Archive Database, and Description fields
Fields marked with one star are required; fields marked with two stars can only be changed after the End date has passed.

Name

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.

Server

Add the name of the target SQL Server instance.

  • If the Log Database is located on the same server as the Nodinite Configuration Database, use localhost or localhost\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 Log Databases whose End date has passed the current date.

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

Check Archive Database when you register an older Log Database, for example one you moved or restored. When you add it, Nodinite checks the database for its content and sets the start and end time from it.

Start date

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.

Start date and read-only End date fields of the Log Database form
The End date field is read-only: it is set from the Start date of the next Log Database, or left empty for the last one.

End date

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 Log Database (the one without an end date) 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.

  1. Make sure the database is empty. Use SSMS or review the content of the Nodinite database report.
    Show Database Report button on the Log Database form
    The database report shows how much data is left in the Log Database.
  2. Click the Delete button.
    Delete button for an archive Log Database
    Delete is not available for the online Log Database.
    A modal asks you to confirm the intent to delete the archive Log Database registration.
    Confirm Deletion dialog for removing a Log Database registration
    The dialog confirms that only the registration is removed, not the physical database.
  3. 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 Server.
  • Check the Remote server checkbox.

Log Database form with an Always-On listener as Server and the remote server checkbox checked
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 Server (and Remote Server) accordingly.

Next Steps