Install Nodinite Log Database
Nodinite Log Databases store the logged events and messages of one environment. They ship with the Nodinite Core Services; you never install them on their own. Follow Install Nodinite v7 for the complete procedure; this page lists what is specific to Log Databases.
What You Set for Log Databases in the Portal
| Setting | Where in the Nodinite Portal |
|---|---|
Environment name, part of every Log Database name (for example Nodinite_Prod_Log_20251028) |
Step 1: Basics |
| SQL Server type: standalone, Always On Availability Group, or Azure SQL Managed Instance | Step 3: Infrastructure |
| SQL Server connection string, now or at install time | Step 3: Infrastructure |
Path to SqlPackage.exe (DacFx) |
Step 3: Infrastructure |
| The Logging Service account, which creates new Log Databases | Step 4: Servers |
Prepare SQL Server first: rights, Linked Servers, MSDTC, and firewall rules are listed in the Prerequisites page.
How Log Databases Are Created
The CLI package (Step 7) installs the Core Services and the Configuration Database, but no Log Database. The Logging Service creates the first Log Database when it starts for the first time, and every later one when the online Log Database gets too large or too old, with the settings in these System Parameters:
- LogDatabaseName (name pattern) and LogLocations (file placement)
- LogDatabaseRecovery (recovery model; the installer sets
FULLfor Always On Availability Groups) - LogAccessRoles and LogServiceUsers (access rights)
- SqlPackageExecutable and SqlPackageParams (schema deployment)
- SizeToSplitDatabaseOn and DaysToSplitDatabaseOn (when to create the next one)
Review them after installation, before much data is logged. The Log Databases overview explains the whole sequence.
Verify the Log Databases
- In the Web Client, Administration › Settings › Log Databases lists one online Log Database with no End Date, once the Logging Service has started.
- The database exists on the SQL Server instance, with the name from LogDatabaseName.
- Log Events you send appear in a Log View.
If the list is empty or the Logging Service reports errors, check the Logging Service account rights in Prerequisites and the Troubleshooting page. Fix this before you go live: a Logging Service that can't create the first Log Database can't create the next ones either, when the online Log Database grows too large or too old.
Note
Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.