Validation and DACPAC Registration
In the new SQL Server instance, the Nodinite version in use needs to be correctly registered.
Note
Nodinite v7: DACPAC version registration is partially automated. The PowerShell installation script handles Agent and Configuration databases automatically. Log Databases require manual script execution from Administration | Settings | Log Databases in the Web Client.
Register DACPAC
For Nodinite v7:
Configuration Database and Agent Databases
- Download the latest Nodinite 7 installation package from the Nodinite portal (or use your currently downloaded version)
- Run the PowerShell installation script:
Nodinite7-%ENVIRONMENTNAME%-Installation.ps1 - The script will automatically detect and register the correct DACPAC versions for:
- Configuration Database
- Agent databases (Monitor Agent, Log Agent)
- Verify registration in Administration | Settings | Log Databases - these databases should show the correct version
Log Databases
- Navigate to Administration | Settings | Log Databases in the Web Client
- For each Log Database, locate the manual update script
- Using a command prompt as the service account for the Nodinite Logging Service, run the provided script
- Verify registration - the version number should match your Nodinite version
- Repeat for each Log Database
For Nodinite v6 (Legacy):
Follow the manual DACPAC registration process described below.
Configuration Database (v6 Legacy)
To register the DACPAC for the Configuration database in Nodinite v6:
- Using a remote desktop session on the Nodinite Server, start a command prompt as the service account used as the installation account for Nodinite
- Navigate to Administration | Settings | Log Databases in the Web Client to obtain the manual update script
- Paste the script for the configuration database and wait for it to finish (review the Manually update database user guide for additional information)
Important
If this step fails, please retry the operation at least once
- Validate registration in Administration | Settings | Log Databases - the version number should match your Nodinite version
Logging Database (v6 Legacy - Manual Process)
For Nodinite v6 using the legacy Install and Update Tool:
- Using remote desktop on the Nodinite Server with the Logging Service, start a command prompt as the service account used for the Nodinite Logging Service
- Use the Install and Update Tool to generate the manual update script
- Paste the script for the logging database and wait for it to finish (review the Manually update database user guide for additional information)
Important
If this step fails, please retry the operation at least once
- Validate registration in the Install and Update Tool - the version number should match your Nodinite version
- Repeat for each Logging Database
Start the IIS - Application Pools
Start all the stopped Nodinite application pools. Review the IIS Authentication settings user guide for additional information.
Important
Do NOT start the Windows Services yet.
Basic Validation Tests
Nodinite v7: Navigate to Administration | Tools | Nodinite Overview in the Web Client to access quick links to all Nodinite Core Services.

Example: Nodinite v7 Overview page with clickable URI links.
Nodinite v6: Navigate to the Overview page in the Web Client (Administration | Tools | Nodinite Overview) to view URIs for all Nodinite Core Services. The URIs are displayed but not clickable—copy and paste them into your browser.

Example: Nodinite v6 Overview page displaying Core Services URIs (copy/paste to use).
Validate that all Core Services are working correctly:
Log API Test
Nodinite v7: Navigate to Administration | Tools | Nodinite Overview in the Web Client, then click the Log API link.
Nodinite v6: From the Overview page, copy the Log API URI and paste it into your browser.
- Browse the Swagger interface or insert a JSON Log Event example, then verify it appears in the Admin Log View
Web API Test
Nodinite v7: Navigate to Administration | Tools | Nodinite Overview in the Web Client, then click the Web API link.
Nodinite v6: From the Overview page, copy the Web API URI and paste it into your browser.
- Using the Swagger feature, perform a test of the Get operations for Roles. All roles should be returned in the response JSON
Web Client Test
Nodinite v7: Navigate to the Web Client home page.
Nodinite v6: From the Overview page, copy the Web Client URI and paste it into your browser.
- Perform a search in the Admin Log View and verify that there are Log Events in the search result
Database Status Verification
From Administration | Settings | Log Databases in the Web Client, verify:
- Server name(s) match the new SQL Server environment
- Database name(s) are correct
- Version numbers match your Nodinite version
- All Log databases are listed as operational
Next Step
Validation successful? Continue with final steps:
- Post-Migration Steps - Cleanup, backups, and monitoring
Related Topics
- Database Migration Overview - Hub page and decision tree
- Planning - Pre-flight checklist
- Local Disk Move - For same SQL instance
- Remote SQL Instance Move - For different SQL instance
- Configuration Changes - Connection strings update
