- 8 minutes to read

How do I Update a Nodinite Log Database?

Keep your Nodinite Log Databases secure, compliant, and up to date with the latest features and performance improvements.

Important

Update Nodinite regularly! We add new features, improve security, and fix bugs so you always benefit from the latest advancements and a superior user experience.

Nodinite Version 7 (Current)

For Nodinite version 7.2.0 and later, use the comprehensive 'Update Log Database' guide built into the Nodinite Web Client Administration interface.

Nodinite Version 6 (Legacy - Deprecated)

Warning

Nodinite v6 is deprecated and pending retirement.
The Install and Update Tool for Nodinite v6 will be retired. Please upgrade to Nodinite v7 for continued support, the latest features, and the superior Update Guide interface.

Note

This section is for Nodinite v6 users only. If you are running Nodinite v7, use the Update Log Database guide instead.

Version 6 Update Overview

In Nodinite v6, all Core Services components except Log Databases are updated using the Install and Update Tool as detailed in the Update Core Service documentation.

Log Databases require manual DACPAC updates due to:

  • Multiple SQL Server instances with different security configurations
  • Large databases where updates may take hours
  • Distributed environments across different networks
  • Web-based Install and Update Tool limitations for long-running processes

Manual Log Database Update Process (Version 6 Only)

Info

You must execute the steps below as the Logging Service account or with an account assigned the sysadmin role.

If you are part of the SYSADMIN fixed server role on all instances hosting a Log Database, you should have sufficient rights to execute the update steps.

Step 1: Select the Environment to update

Start by selecting the Environment to update:

Select Environment
Example list of installed Environments; select the one to update.

Step 2: Retrieve DACPAC command

The logic behind the scenes uses the value from the LogDatabaseRecovery system parameter to present the correct script information for Log Databases.

The Manual update button is not on the screen if there is no mandatory update available. Otherwise, use the small "..." button to open the modal for optional updates.

Click the button to open a modal with the DACPAC command to execute:

Manual Update Button
The 'Manual update' button is only available if there's a mandatory update to apply.

Copy ALL of the content from the text box:

Update the Log Database modal
Repeat the step and copy the command text with unique settings for each Log Database.

Info

The script has two paths, one for the SQLPackage.exe executable and the second is about the .DACPAC file.

If you execute the update script on another server, you can click the download button to get the proper .DACPAC file:

Important

You must change the path content if you intend to execute the script on another server; please revise and verify the new script accordingly.

Step 3: Execute command

Note

  • You must perform the update using a command prompt. Do not use the SQL MMC (SSMS) or Powershell.
  • This step assumes you run the command prompt logged in on the Nodinite server with the Install and Update Tool. It is possible to copy the DACPAC file to another server and adjust folder paths provided to suit the target environment.

Open an administrative command prompt as either the account running the Logging Service or with another account with at least equal rights or an account part of the SYSADMIN fixed server role on the SQL instance with the Log Databases to update.

Paste the command string from step 2 and press enter:

Info

You should see text rolling on the screen as the update progresses. This process may take seconds for small databases up to hour(s) for large databases or SQL Servers with poor disk IO performance.

Repeat "Step 2" and "this Step" for all Log Databases listed for an update (with the Manual Update button):

Info

The Configuration Database may be in the list with the Manual Update button.

[!NOTE] This database is usually updated by the system during the update process. Use the script only if there's a problem executing the update from the Install and Update Tool.

You may need to perform a shrink operation. Make sure to review the allocated disk space on your SQL Server instance with the updated Nodinite Log Databases.

Frequently asked questions

Find solutions to common problems and answers to frequently asked questions in the Nodinite Log Databases FAQ, available in the Troubleshooting user guide.

Why must I update Nodinite Log Databases manually?

Manual Log Database updates protect your production environment from common risks:

  • Disk space exhaustion – Large databases require significant free space during schema updates and index rebuilds. Automatic updates could fail mid-process if disk space runs out.
  • Long processing times – Updates can take hours for large Log Databases, potentially timing out web-based interfaces.
  • System resource consumption – Database migrations consume CPU, memory, and disk I/O, which could impact production operations if executed during business hours.
  • Distributed environments – Multiple Log Databases may exist across different SQL Server instances, networks, and security configurations, making centralized updates impractical.

Tip

Golden Rule: If your current configuration works, don't change it unless there's a mandatory update or specific new feature you need.

Which System Parameters must be configured before manual updates?

Critical: Review and verify these System Parameters before executing manual Log Database update scripts:

These parameters directly affect DACPAC deployment scripts. Incorrect settings can cause update failures or suboptimal database configurations.

Info

All System Parameters are documented in detail on their individual pages. Review the System Parameters Overview for complete descriptions.

Where do I update Log Databases in different Nodinite versions?

The manual DACPAC execution process is identical in both versions—you copy the generated command and execute it in a command prompt. The difference is where you retrieve the command:

In both versions, you copy-paste the command and execute it manually due to the risks of long processing times, disk space requirements, and resource consumption.

What are the sqlpackage.exe requirements?

Nodinite v7:

  • The Nodinite Logging Service uses a NuGet package for Log Database updates and does not directly require sqlpackage.exe.
  • However, the Nodinite application server must have the latest Microsoft SqlPackage installed for PowerShell 7 update scripts that manage Configuration Database and Monitor/Log Agent databases.
  • Download the latest SqlPackage from Microsoft SqlPackage Download.

Nodinite v6 (Legacy):

  • The Logging Service used the System Parameter SqlPackageExecutable to locate sqlpackage.exe for DACPAC deployments.
  • Manual update scripts require correct paths to both SqlPackage.exe and .DACPAC files.

Why does my manual update script fail?

Common issues when executing DACPAC update scripts:

  • SqlPackage not installed or outdated – Ensure the latest Microsoft SqlPackage is installed on the server executing the script. Download from Microsoft SqlPackage Download.
  • Incorrect SqlPackage.exe path – Verify the path in the copied script matches the actual SqlPackage.exe location on the execution server.
  • DACPAC file not accessible – Ensure the .DACPAC file path is correct and accessible from the server executing the script.
  • Insufficient permissions – You must be a member of the SQL Server sysadmin fixed server role on the target instance.
  • Always On Availability Groups (AOAG) – Log Databases must be manually removed from AOAG synchronization before updates, then manually re-added after successful completion.
  • Disk space exhaustion – Verify sufficient free disk space for schema updates, index rebuilds, and transaction log growth during the update process.
  • Recovery model mismatch – The script uses the LogDatabaseRecovery System Parameter value. If your remote SQL Server instance has a different recovery model configured, update the System Parameter before retrieving the script.
  • System Parameters misconfiguration – LogLocations, DatabaseMaintenance, or other parameters may conflict with your SQL Server configuration.

Tip

Best practice: Execute the update script as the Logging Service account to verify it still has appropriate permissions. Service account rights may change over time due to organizational policy updates.

Warning

Always test update scripts in a non-production environment first. Backup all databases before executing updates.

Tip

Disk space management: Nodinite does not automatically remove old Log Databases. Over time, historical databases can consume significant disk space even if empty. Consider automating cleanup with the Automating removal of old Log Databases guide to prevent disk space exhaustion.

Next steps

Nodinite Version 7

Nodinite Version 6 (Legacy)

Nodinite Version 7

Nodinite Version 6 (Legacy)