- 2 minutes to read

Update the Nodinite Configuration Database

The Nodinite Configuration Database is part of the Nodinite Core Services and is updated together with them; you never update it on its own. Follow Updating Nodinite v7 for the complete procedure; this page lists what is specific to the Configuration Database.

What You Set for the Configuration Database in the Portal

Setting Where in the Nodinite Portal
The environment to update Updating Nodinite v7, Step 1 (the Environment you registered in Step 1: Basics)
SQL Server type and connection string Step 3: Infrastructure
Path to SqlPackage.exe (DacFx) used to deploy the new schema Step 3: Infrastructure

Download the new ZIP for the environment (Step 2) and run the CLI workflow (Step 3).

What the CLI Does for the Configuration Database

  • deploy-environment deploys the new Configuration Database schema (Dacpac) with SqlPackage.exe, as the user who runs the CLI. That user needs the SQL Server rights in SQL Server Sysadmin Requirements.
  • Before it applies schema changes, the CLI asks you to confirm a verified backup: back up now, continue, or abort.
  • Your configuration, System Parameters values, and the list of Log Databases are kept.

Tip

Run validate and deploy-environment --dry-run first, and test the update in a non-production environment before you update production.

Verify the Update

  • The CLI finishes without errors. If it reports file locks, see File Locks Detected.
  • The Web Client loads and Administration › Settings › System Parameters shows your values.
  • Administration › Settings › Log Databases shows whether a Log Database schema update is available. Log Databases are updated separately with the Update Log Database guide.

Note

Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.

Next Steps