- 4 minutes to read

Add or manage a Nodinite Log Database

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

The administration pages in the Web Client are typically used when you move a database from one SQL Server Instance to another or when you remove (Delete) a database.

When you add or remove a Nodinite Log Database from within the Nodinite Web Client, the physical database within Microsoft SQL Server is not touched in any way.

The configuration gives Nodinite knowledge on the whereabouts of the physical Log Databases.

This means that you can safely move Log Databases from one SQL Instance to another, and then simply change its configuration accordingly. Renaming the Log Databases is also a possible scenario.

Tip: Move old databases to your SQL Hotel where disk might be cheaper

Tip: Move old databases to better utilize hardware resources

Tip: Empty databases can safely be removed

Instructions

A name for the Log Database is mandatory.

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

Add Log Database

Name

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

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

Server

Add the name of the target SQL Server instance.

Read-Only

Check this checkbox to make the Log Database read-only. Nodinite will use this database only to search for data (No operations like re-index, remove, or add will then be performed by internal maintenance)

Note: The Read-Only flag can only be checked for Log Databases if the 'End date' has passed the current date.

Remote Server

Check the checkbox if the Log Database is located on a remote SQL Server instance in relation to the Nodinite Configuration Database.

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.

Start Date

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. Nodinite must always know about at least one Log Database to insert new Log Events to.

Description

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

Delete

A Nodinite administrator can Delete Log Databases. Deleting a Log Database will prevent users from accessing the data from Nodinite Web Client and the Web API.

The Log Database without an end date cannot be deleted.

Note: The physical database will not be deleted in SQL Server. You must delete it manually from within the SQL MMC SSMS.

Always-On

If the Log Database is hosted on a SQL Server Always-on availability group, then you must provide the following details:

  • The name of the Always-on group (usually the listener name)
  • Check the Remote server checkbox
    alwayson
    Example settings for SQL Server Always-on Availability group

You must make sure the linked servers are setup using the listener name, in which case you also need to review the 'About Always-On' user guide

Troubleshooting

The following user guides are usually very helpful:

How do I move a Nodinite Log Database?

This is detailed in the 'Moving Nodinite Databases' user guide.


Next Step

Log

Log Agents
Log API