- 0 minutes to read

Add or manage a Nodinite Log Database

On this page, you will learn how to manage Nodinite Log Databases.

The configuration tells Nodinite the whereabouts of the physical Log Databases.

Use the administration pages in the Web Client to:

Manage the location information when moving the database from one SQL Server Instance to another.
Remove (Delete) a database.

You do not touch the physical database within the Microsoft SQL Server instance in any way when you add or remove a Nodinite Log Database from within the Nodinite Web Client. The physical database is created by the Nodinite Logging Service or by manually executing scripts.

You can safely move Log Databases from one SQL Server Instance to another and then change its configuration accordingly. Renaming the Log Databases is also a possible scenario.

Move old databases to a SQL Server hotel where disk might be cheaper.

Move old databases to utilize hardware resources better.

Safely Delete empty databases.

Instructions

A name for the Log Database is mandatory. To insert new Log Events; Nodinite must always know about at least one Log Database.

If you create the Log Databases manually, you must set the active intervals (Start Date and End Date).

The following fields exist for a Log Database:

Database Name
Server Name (might include the instance name)
Description
Start Date
End Date
Read-Only

Name

Enter the database name. This field is required to create the Log Database configuration.

The default format is: NodiniteLog_%ENVIRONMENT%_STARTDATE, for example NodiniteLog_Test_20120517

Server

Add the name of the target SQL Server instance.

If the Log Database is located on the same server as the Nodinite Configuration DatabaseIt should be:
- localhost or localhost\instancename
Otherwise, enter the name using a linked server. Remote Log Databases are accessed using the concept of linked servers.

Read-Only

Check this checkbox to make the Log Database read-only.

When checked, there is no internal maintenance and operations like re-index, delete/truncate, or insert are suspended.

Note
The Read-Only flag can only be checked for Log Databases if the '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 requires a linked server between the SQL Server instance with the configuration database and the remote Log Database.

Start date

For a historical (archive) Log Database, this is the start date for Log Events. For future Log Databases, this value makes sure that future events enter the correct target Log Database when the time comes.

End date

For a historical (archive) Log Database, this is the end date for Log Events in that particular database.

The topmost (last or current) Log Database is not allowed to have an end date.

Description

The optional field Description can be used to give this configuration a user-friendly meaning.

Delete Log Database

As time goes by, the historical Nodinite Log Databases gets smaller and smaller. At some point in time the are even empty. The Nodinite Administrator can and should remove empty Log Databases. Deleting a non-empty Log Database results in data loss and prevents users from accessing the data from Nodinite Web Client and the Web API.

The current Nodinite Log Database (the one without an end date) cannot be deleted. The physical database will not be deleted in SQL Server. You must delete it manually from within the SQL MMC SSMS.

To remove an empty historical Nodinite Log Databases, please follow the instructions in sequence:

First, make sure the database is indeed empty. Use SSMS or review the content of the Nodinite Database report
Next, click on the Delete button

Then a modal presents where you need to confirm the intent to delete the historicalNodinite Log Databases.
Now, remove the database from the SQL Server instance using SSMS.