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.
- 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
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)
- Start Date
- End Date
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
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:
- Otherwise, enter the name using a linked server. Remote Log Databases are accessed using the concept of linked servers.
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.
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.
The topmost (last or current) Log Database is not allowed to have an end date.
The optional field Description can be used to give this configuration a user-friendly meaning.
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.
To remove an empty historical Nodinite Log Databases, please follow the instructions in sequence:
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.
If you are using SQL Server Always-on availability group to host the Log Database; Then you must provide the following details:
- Enter the name of the Always-on group (usually the listener name).
- Check the Remote server checkbox.
The following user guides are usually helpful: