Uninstall Log Databases
Nodinite Log Databases are part of the Nodinite Core Services and are removed with them by the v7 CLI. Follow Uninstall Nodinite v7 for the complete procedure; this page lists what is specific to Log Databases.
What the CLI Does with Log Databases
| CLI command | Log Databases |
|---|---|
uninstall |
✅ Kept. Only the Core Services are removed. |
uninstall with --delete-databases (see Remove Database Option) |
❌ Core Services databases are dropped; you lose all logging data. |
teardown-environment |
Kept, unless you add --delete-databases, which requires --confirm with the environment name. |
Important
Back up your data! Export critical logs and audit trails before uninstalling, and run destructive commands with
--dry-runfirst. Archive Log Databases on other SQL Server instances, created by the Logging Service over time, may not be covered by the CLI; check every instance listed under Administration › Settings › Log Databases and remove leftovers yourself.
Tip
For routine maintenance: Nodinite does not automatically remove old Log Databases. To free disk space, use the Automating removal of old Log Databases guide instead of a full uninstallation.
Clean Up SQL Server
The CLI doesn't remove SQL Server objects outside the databases. Review the SQL Server Cleanup checklist: logins for the accounts in LogServiceUsers, backup jobs, Linked Servers to remote Log Database instances, and SPNs created for Nodinite. Also remove the folders configured in LogLocations when they are no longer used.
Verify the Removal
- With
--delete-databases: no database named by the LogDatabaseName pattern (for exampleNodinite_Prod_Log_…) remains on any SQL Server instance. - Without it: the Log Databases still exist, and no Core Service writes to them.
Note
Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.
Contact Our Support
If you have questions or encounter issues uninstalling the Log Databases, contact our expert team, read more on the Support page.