About manually updating the Configuration Database and Log Databases (Version 6 Only)

Warning

This guide is for Nodinite v6 only (Legacy – Deprecated).

If you are using Nodinite v7, database updates have changed:

• Configuration Database – Updated automatically by the CLI in the generated Nodinite Portal package, run in elevated PowerShell 7
• Log Databases – Use the built-in Update Guide in the Web Client (Administration | Settings | Log Databases)

Do not use this manual DACPAC process for v7.

Nodinite v7 users: See Update Nodinite v7 for Core Services updates and Update Log Database for Log Database updates

Note

This section is for Nodinite v6 users only. Nodinite v6 and its Install and Update Tool are no longer supported. Follow Updating from v6 to v7 for continued support and automated database updates.

Which Tool Updates Which Database in v7

Diagram: in Nodinite v7, the CLI (blue) updates the Configuration Database and the Monitoring Databases of agents in the package when you update Nodinite; the Update Log Database guide (orange) generates the scripts that update existing Log Databases; and the Logging Service creates new Log Databases with the current schema, starting with the first one. None of these need the v6 procedure below.

Version 6 Manual Update Overview

This legacy guide explains how to manually update the Configuration Database and Log Databases in Nodinite v6 using DACPAC and the Update Tool.

Note

Nodinite v7 changed both update procedures:

• Configuration Database is now updated automatically by the CLI in the generated package
• Log Databases use the Update Log Database guide in the Web Client, which generates the scripts to run

• ✅ Enables updates in highly secure or restricted SQL environments
• ✅ Supports parallel updates for multiple Log Databases
• ✅ Avoids browser timeouts and long-running web transactions
• ✅ Step-by-step, command-line instructions for full control

Nodinite v6 provides built-in support for updating the Configuration Database using the web-based Update Tool. However, you must always manually update the Log Databases. Manual updates are also required in scenarios such as:

• Security restrictions—only a SQL DBA has sufficient rights to perform the update
• Long execution times—web-based updates may time out or block the browser
• Parallel execution—updating many Log Databases at once

When performing a manual update, use the Nodinite Logging Service service account or an account with sysadmin rights on the target Microsoft SQL Server.

For complete guidance on when sysadmin is required and what to configure when it is not available, see SQL Server Sysadmin Requirements.

To start a manual update:

1. Click the update button ( or ) in the Update Tool.
2. A modal window opens with a ready-to-run script.
3. Run this script from a command prompt as the Logging Service account.

Example: Manual update button locations in the Nodinite v6 Update Tool.

You must have the DACPAC binaries installed. See the SQL Server Package (DACPAC) user guide for details.

Update Modal Example

Select the appropriate version for the update. The default is the highest available version.

Example: Update modal for Configuration Database showing version selection and generated script.

Config Database Example

The following is a sample command for updating the Configuration Database:

"C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe" /Action:Publish /TargetDatabaseName:"NodiniteConfig_Dev" /TargetServerName:"localhost" /SourceFile:"C:\Program Files\Nodinite\Nodinite Update\UpdateClient\App_Data\files\versions\6.1.0.37\Nodinite.ConfigDatabase.dacpac" /SourceEncryptConnection:true /TargetEncryptConnection:true /SourceTrustServerCertificate:false /TargetTrustServerCertificate:true /Properties:RegisterDataTierApplication=True /Properties:BlockOnPossibleDataLoss=False /Properties:BlockWhenDriftDetected=False /Properties:DropIndexesNotInSource=True /Properties:DropConstraintsNotInSource=True /Properties:ScriptNewConstraintValidation=False

Ignore DACPAC Options

^{New 6.1.0.4}
Check the Ignore DACPAC Options box to skip database options like collation and recovery mode during the update.

Log Database Example

"C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe" /Action:Publish /TargetDatabaseName:"NodiniteLog_Dev_20220104" /TargetServerName:"localhost" /SourceFile:"C:\Program Files\Nodinite\Nodinite Update\UpdateClient\App_Data\files\versions\6.1.0.37\Nodinite.LogDatabase.Full.dacpac" /SourceEncryptConnection:true /TargetEncryptConnection:true /SourceTrustServerCertificate:false /TargetTrustServerCertificate:true /Properties:RegisterDataTierApplication=True /Properties:BlockOnPossibleDataLoss=False /Properties:BlockWhenDriftDetected=False /Properties:PopulateFilesOnFilegroups=False /Properties:DropIndexesNotInSource=True /Properties:DropConstraintsNotInSource=True /Properties:ScriptNewConstraintValidation=False /v:CustomPathData="null" /v:CustomPathImagedata="null" /v:CustomPathIndex="null"

Next Steps

Nodinite Version 7 (Recommended)

• Update Nodinite v7 – Automated Core Services and Configuration Database updates with the CLI in the generated package
• Update Log Database – Use the Update Guide in Web Client for Log Database updates (v7.2.0+)

Nodinite Version 6 (Legacy)

• Update Nodinite v6 – Legacy update instructions (deprecated)

Related Topics

Nodinite Version 7

• Update Nodinite v7 – Primary update documentation
• Update Log Database – Update Guide for v7 Log Databases

Nodinite Version 6 (Legacy)

• Release Notes – Legacy v6 release notes
• Configuration Database
• Log Databases