- 2 minutes to read

Uninstall Configuration Database

The Nodinite Configuration Database is part of the Nodinite Core Services and is removed with them by the v7 CLI, never on its own. Follow Uninstall Nodinite v7 for the complete procedure; this page lists what is specific to the Configuration Database.

What the CLI Does with the Configuration Database

CLI command Configuration Database
uninstall ✅ Kept. Only the Core Services are removed, so you can reinstall later and keep your configuration.
uninstall with --delete-databases (see Remove Database Option) ❌ Dropped with the other Core Services databases. You lose all configuration, System Parameters, and Repository, logging, and monitoring data.
teardown-environment Kept, unless you add --delete-databases, which requires --confirm with the environment name.

Important

Back up the Configuration Database before you use --delete-databases. Dropping it can't be undone. Run the command with --dry-run first.

Clean Up SQL Server

The CLI doesn't remove SQL Server objects outside the databases. Whether you kept or dropped the Configuration Database, review the SQL Server Cleanup checklist: SQL logins for the service accounts, backup jobs, Linked Servers, and SPNs created for Nodinite.

Verify the Removal

  • With --delete-databases: the database named after your environment (for example Nodinite_Prod_Config) no longer exists on the SQL Server instance.
  • Without it: the database still exists, and no Core Service connects to it any more.

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 Configuration Database, read more on the Support page or use the Nodinite Portal.

Next Steps