- 7 minutes to read

What is a Log Database?

Nodinite Log Databases deliver scalable, secure, and high-performance storage for all your integration data. This page explains how Log Databases work, how they grow with your business, and how they keep your data protected and accessible for compliance, analytics, and troubleshooting.

What you'll learn on this page:

  • ✅ Effortlessly scale storage for unlimited integration data
  • ✅ Maintain high performance as data volumes grow
  • ✅ Secure sensitive data with built-in obfuscation
  • ✅ Automate archiving and partitioning for compliance and cost control
  • ✅ Simplify administration with seamless integration and self-healing features

Nodinite logs events and messages from your system integration brokers (Mule, BizTalk, ...) and custom solutions using Log Events sent to the Log API or picked up by Log Agents. All this data is persisted for long-term storage in SQL Server-based databases known as Log Databases. As data volumes grow, traditional relational databases can suffer performance hits, and SQL Express limits storage to 10GB per database. Nodinite overcomes these limitations by automatically spawning new Log Databases as they grow too large or too old. You never need to worry about which database your data is in—Nodinite manages it all behind the scenes using the Configuration Database.

Understanding Log Databases

The Configuration Database interacts with and depends on the Log Databases using Linked Server connections and configured security settings. The Core Services Overview and 'Prerequisites' pages detail all required SQL, Windows, and firewall settings. Having the Log Databases on the same SQL Server instance as the Configuration Database reduces administration for firewalls, distributed transactions, and more.

graph LR subgraph "SQL Server" roConfigDatabase(fal:fa-database Configuration database) --- | Linked Server | roLogDatabase(fal:fa-database fal:fa-database fal:fa-database Log databases) end subgraph "Historical SQL Server" roConfigDatabase --- | Linked Server | roLogDatabase2(fal:fa-database fal:fa-database fal:fa-database fal:fa-database fal:fa-database fal:fa-database Log databases) end

Overview of Nodinite Configuration Database interacting with the Log Databases using a linked server

There is always exactly one online (active) Log Database, which receives new data, and any number of archive Log Databases, which hold older data and are still searched from Log Views. Administrators see the list in the Web Client under Administration › Settings › Log Databases.

Sensitive data within the Log Databases is protected using an obfuscator, so a SQL DBA cannot read the content or context properties of messages like patient journals and salary payments.

Data is partitioned over time into multiple Log Databases. This feature improves performance and enables virtually unlimited storage, both horizontally and vertically. Your hardware is the limit, not Nodinite

System administrators can put historical Log Databases in read-only mode.

Large data volumes and high transaction counts require scaling hardware and software for the Nodinite environment. See 'Prerequisites' for more information.

How a New Log Database Is Created

The installer doesn't create a Log Database: the Logging Service creates the first one when it starts for the first time, with the same steps as below. With the right access rights, automatic log archiving is built into Nodinite. Log Databases split on Size and/or Time, governed by System Parameters stored in the Configuration Database. When the online Log Database is larger than SizeToSplitDatabaseOn or older than DaysToSplitDatabaseOn, the Logging Service creates the next one:

Administration > Settings > Log Databases lists the online Log Database Nodinite_DEV_Log_20241113 without an End Date and two archives, then the System Parameters SizeToSplitDatabaseOn, DaysToSplitDatabaseOn and LogDatabaseName, and the online Log Database opened with its Start Date and an empty End Date, animated walkthrough (7.12)
Animated walkthrough: where a new Log Database shows up and which System Parameters decide when it is created and what it is called. Nothing is changed in the walkthrough.

  1. Open Administration > Settings > Log Databases. The online Log Database has no End Date; the others are archives.
  2. In System Parameters, filter on SplitDatabaseOn: SizeToSplitDatabaseOn (GB) and DaysToSplitDatabaseOn decide when to split.
  3. Filter on LogDatabaseName: LogDatabaseName is the name of the next one, Nodinite_DEV_Log_{year}{month}{day}.
  4. Back in the Log Databases list, a new Log Database appears with its name and Start Date, and the previous one gets an End Date.
  5. Open the online Log Database: it has a Start Date and no End Date while it is online.

The Logging Service checks these conditions every hour:

  • No Log Database registered at all: it creates the first one on the Configuration Database's SQL Server, reached through the linked server in SqlServer, with a Start Date seven days back.
  • No online Log Database (every registration has an End Date): it creates the next one, starting at the newest End Date.
  • Size: the online Log Database is larger than SizeToSplitDatabaseOn, set in GB.
  • Age: the days since the online Log Database's Start Date (UTC) reach DaysToSplitDatabaseOn, unless a Log Database is already registered for the next day.

Each run writes a Log Audit, also when it skips creating one.

The SizeToSplitDatabaseOn page has the step-by-step sequence.

If Nodinite is not given elevated rights, your organization may need to create new Log Databases manually to avoid performance issues. See Create new Log Databases Manually and always follow the naming scheme in the LogDatabaseName System Parameter.

Log Database Naming

New Log Databases are named by the LogDatabaseName pattern, which the installer sets to Nodinite_<EnvironmentName>_Log_{year}{month}{day}, for example Nodinite_Prod_Log_20251028. {year}{month}{day} is the date (UTC) the Logging Service creates the database, not its Start Date. The first Log Database starts seven days earlier than it is created, so Nodinite_DEV_Log_20241113 has the Start Date 2024-11-06. The environment part comes from EnvironmentName; it is not validated, so SQL Server naming rules are the limit. Use letters, digits, and hyphens, and don't change it after installation.

Note

Existing databases are not renamed when you upgrade. Log Databases created by Nodinite v6 keep their NodiniteLog_<EnvironmentName>_{date} names, and the Configuration Database keeps NodiniteConfig_<EnvironmentName> (new installations use Nodinite_<EnvironmentName>_Config).

System Parameters for Log Databases

These System Parameters control how Log Databases are created and maintained. The Logging Service reads them (except EnvironmentName, which reaches the names through the LogDatabaseName pattern), and a change takes effect within about 15 seconds without a restart; most apply to the next Log Database it creates. Change them as described in Manage System Parameters.

System Parameter Purpose
SizeToSplitDatabaseOn Maximum size (GB) of the online Log Database before a new one is created
DaysToSplitDatabaseOn Maximum age (days) of the online Log Database before a new one is created
LogDatabaseName Naming pattern for new Log Databases
EnvironmentName Environment name, part of the Log Database names
LogLocations Folders for the data, index, and transaction log files of new Log Databases
LogDatabaseRecovery Recovery model (SIMPLE or FULL) of new Log Databases; also used by the Update Log Database scripts
LogAccessRoles Database roles granted on new Log Databases
LogServiceUsers Accounts that get those roles
AvailabilityGroupBackupPath Backup share used when a new Log Database is created on an Always On Availability Group
DatabaseMaintenance Nightly reindexing, and shrinking of archive Log Databases
SqlPackageExecutable Path to SqlPackage.exe used to deploy new Log Databases
SqlPackageParams Connection security options passed to SqlPackage.exe
SqlServer The SQL Server and Linked Server names used for Log Databases (change only with Support)

Recovery Model, Always On, and SQL Server Options

Install, Update, and Remove Log Databases

Frequently Asked Questions

Find answers on size, recovery models, and high availability in the Log Databases troubleshooting guide.

Next Steps