- 0 minutes to read

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 PowerShell 7 installation scripts from the Nodinite Portal
  • 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. The Install and Update Tool for Nodinite v6 is deprecated and will be retired. Please upgrade to Nodinite v7 for continued support and automated database updates.

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 PowerShell 7 scripts
  • Log Databases use the Update Guide wizard in the Web Client (no manual DACPAC commands needed)

✅ 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.

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.

Manual Update Buttons (6.1.0.4)
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.

Config manually update Config database (6.1.0.4)
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 Step

  • Update Nodinite v7 – Automated Core Services and Configuration Database updates via PowerShell 7 scripts
  • Update Log Database – Use the Update Guide in Web Client for Log Database updates (v7.2.0+)

Nodinite Version 6 (Legacy)

Nodinite Version 7

Nodinite Version 6 (Legacy)