Remote SQL Instance Move

Migrate your Nodinite databases to a different SQL Server instance with confidence using this comprehensive technical guide. Whether you're upgrading SQL Server versions, consolidating instances, or moving to new hardware, this guide provides the detailed steps and context you need for a successful migration.

Understanding the Migration Process

When moving Nodinite databases to a different SQL Server instance, you're performing a complete relocation of all database files and their associated configurations. This differs from a Local Disk Move where databases stay on the same instance.

Migration workflow from source to destination SQL Server instance with all critical steps.

What Gets Migrated

Migration Approach: Detach/Attach vs Backup/Restore

Tip

Recommended approach: Use detach/attach for same SQL Server versions (faster). Use backup/restore when upgrading SQL Server versions or when you want to keep the source instance operational during migration.

Stop Services

Before you proceed with the database move operation, stop all the Nodinite services. Nodinite is not available for end-users during the move operation.

Stop the IIS - Application Pool(s)

Stop all the application pools. There can be multiple Application Pools depending on your actual configuration. Review the IIS Authentication settings user guide for additional information.

Example of IIS Application Pools management console.

Note

Nodinite v7: All app pools can be stopped.
Nodinite v6: Stop all app pools except for the Update Client app pool.

Stop the Logging Service

Nodinite v7: Navigate to Administration | Settings | Log Databases in the Web Client, then use the service control buttons to stop the Logging Service. The stop operation may take some time (0-120 seconds is common).

Nodinite v6: Use either the Windows Services management console or the Nodinite Install and Update Tool.

Example of stopping the Logging Service from Windows Services console.

Stop the Monitoring Service

Nodinite v7: Navigate to Administration | Settings | Log Databases in the Web Client, then use the service control buttons to stop the Monitoring Service. This may take some time (0-60 seconds is usual).

Nodinite v6: Use either the Windows Services management console or the Nodinite Install and Update Tool.

Example of stopping the Monitoring Service from Windows Services console.

Remove DACPAC Information from the Old Database Server

To make your old SQL environment as clean as possible, you will next remove the installed DACPAC version information for databases no longer in the instance.

You can either use the automated script below or the manual approach described below. If you go for the manual approach, the databases must still exist

Tip

If you are decommissioning the old SQL Server environment then you can safely ignore this step.

The information about the currently installed DACPAC version is present in the Nodinite Administration | Tools | Nodinite Overview.

Example of DACPAC version information displayed in Nodinite Overview page.

Automated DACPAC Removal

Execute the following SQL command to remove DACPAC information for ALL databases that no longer exist on the instance. Run this script from SSMS against the master database:

-- Remove DACPAC information for databases no longer present on the instance
DELETE FROM msdb.dbo.sysdac_instances
WHERE instance_id NOT IN (
    SELECT instance_id
    FROM msdb.dbo.sysdac_instances dac
    WHERE EXISTS (
        SELECT 1 FROM sys.databases db
        WHERE db.name = dac.instance_name
    )
)

-- Verify deletion
SELECT COUNT(*) AS RemainingDACPACRecords FROM msdb.dbo.sysdac_instances

This script:

• Identifies DACPAC records for databases that no longer exist on the SQL instance
• Removes only the orphaned DACPAC information
• Preserves DACPAC records for databases that still exist
• Returns the count of remaining DACPAC records for verification

If you are still on Nodinite version 6, the Install and Update Tool should now display 0.0.0.0 for all moved Nodinite databases.

Example of empty DACPAC version information after removal.

Manual DACPAC Removal per Database

If you prefer the manual approach, you can remove each database's Data-tier application using SSMS. On the old SQL Server instance; Right-click on each Nodinite database (those part of the move):

Example of 'Delete Data-tier Application' context menu option in SSMS.

Then, the 'Delete Data-tier Application' Wizard will start:

Example of Delete Data-tier Application wizard introduction screen.

Click the Next button for the Summary

Example of Delete Data-tier Application wizard summary screen.

Click the Next button for the Finish

Example of Delete Data-tier Application wizard completion screen.

Repeat this step for ALL Nodinite log- and configuration databases.

Detach Databases

Please make a note of who is the DBOwner on each database to be moved prior to detaching them. This information may come in handy in later steps.

If your new SQL instance is compatible, it is faster to detach and later re-attach the databases.

1. Detach the databases included in the move operation with the 'drop existing connections option' checked.
2. Copy or move the data files to the new destination.
3. Attach the data files to the new SQL Server instance.
4. Optionally rename the databases (for example, when migrating/updating from Integration Manager to Nodinite).

Important

If your new environment cannot attach the old files, you must perform a backup/restore operation.

Apply User Rights

Next, you need to fix/adjust the privileges set on the re-attached or restored databases.

Configuration Database

Please make sure to set the Nodinite install account as the database owner (DBO) on the Nodinite Configuration Database.

Logging Databases

For each Logging Database, make sure to make the account used for the Logging Service the database owner (DBO).

Restart Services

After completing all configuration changes and validation steps:

Start the Logging Service

Nodinite v7: Navigate to Administration | Settings | Log Databases in the Web Client, then use the service control buttons to start the Logging Service.

Nodinite v6: Use either the Windows Services management console or the Nodinite Install and Update Tool.

Start the Monitoring Service

Nodinite v7: Navigate to Administration | Settings | Log Databases in the Web Client, then use the service control buttons to start the Monitoring Service.

Nodinite v6: Use either the Windows Services management console or the Nodinite Install and Update Tool.

Start the IIS Application Pools

Start all the previously stopped Nodinite application pools. Review the IIS Authentication settings user guide for additional information.

Next Step

Database preparation complete? Continue with:

• Configuration Changes - Update connection strings for all services

Related Topics

• Database Migration Overview - Hub page and decision tree
• Planning - Pre-flight checklist
• Local Disk Move - For same SQL instance
• Validation and DACPAC Registration - Testing and verification
• Post-Migration Steps - Cleanup and optimization