- 4 minutes to read

SQL Server Database Migration

Migrate your Nodinite SQL Server databases with confidence using this comprehensive guide. Whether you''re moving to a new disk volume or migrating to an entirely new SQL Server instance, we''ll guide you through every step of the process.

✅ Step-by-step planning checklists
✅ Scenario-specific migration paths (local disk or remote instance)
✅ Secure configuration updates (v6 and v7)
✅ Complete validation and testing procedures
✅ Post-migration optimization and monitoring

Choose Your Migration Path

What are you moving?

flowchart TD A["Where are your databases now?"] --> B{"What''s your target?"} B -->|Same SQL instance
Different disks| C["Local Disk Move"] B -->|Different SQL instance
Same or different server| D["Remote SQL Instance Move"] C --> E["→ Fast path: Detach & Reattach"] D --> F["→ Full migration: Comprehensive steps"] style C fill:#e1f5ff style D fill:#f3e5f5

Migration Phases Overview

Every migration follows these core phases, regardless of your scenario:

Phase 1: Planning & Preparation

Before you touch anything — Verify prerequisites, inform stakeholders, and prepare the target environment.

→ 1. Planning Guide — Pre-flight checklist and prerequisites

Phase 2: Migration Execution

Stop services and move data — The actual migration depends on your scenario.

  • Local Disk Move → Detach/Reattach on same SQL instance
  • Remote SQL Instance Move → Backup/Restore to new server, with detailed steps

→ 2. Local Disk Move — Move to different disks on same instance → 3. Remote SQL Instance Move — Migrate to new SQL Server

Phase 3: Configuration Updates

Update connection strings — Point Nodinite services to new database locations.

→ 4. Configuration Changes — Update all service connection strings (v6 & v7)

Phase 4: Validation & DACPAC Registration

Test everything — Verify services start and databases are operational.

→ 5. Validation & DACPAC Registration — Register versions and run tests

Phase 5: Post-Migration Optimization

Optimize and maintain — Backup, monitor, and tune the new environment.

→ 6. Post-Migration Steps — Backups, monitoring, and performance tuning

Quick Decision Tree

Scenario Start Here Key Phases
Moving to different disks on same SQL instance Local Disk Move Stop services → Detach → Move files → Reattach → Restart
Moving to different SQL Server instance Planning → Remote Move Plan → Prepare instance → Backup → Restore → Configure → Validate
Upgrading to newer SQL Server version Planning → Remote Move Verify compatibility → Prepare → Backup → Restore → Test
Consolidating multiple instances Planning → Remote Move Plan carefully → Prepare → Backup each → Restore to new instance

Key Concepts

Local Disk Move

Use when: Moving to different disk volumes on the same SQL Server instance

Advantages:

  • ✅ Fast and simple
  • ✅ No service reconfiguration needed (server name unchanged)
  • ✅ Lower risk
  • ✅ Minimal downtime

What happens:

  1. Stop Nodinite services
  2. Detach databases from current disks
  3. Move database files to new disks
  4. Reattach databases
  5. Restart services

Remote SQL Instance Move

Use when: Moving to any different SQL Server instance (new server, upgrade, consolidation)

Advantages:

  • ✅ Complete infrastructure refresh
  • ✅ Version upgrades supported
  • ✅ No downtime on old server
  • ✅ Easy rollback (old server still available)

What happens:

  1. Plan and prepare new SQL instance
  2. Stop Nodinite services
  3. Backup databases from old instance
  4. Restore to new instance
  5. Update all Nodinite configuration (connection strings, encryption)
  6. Validate and test
  7. Decommission old instance

Important: Nodinite v6 vs v7 Differences

Encryption changes between versions:

  • Nodinite 7: Uses certificate-based encryption (automatic, stored in Windows Certificate Store)
  • Nodinite 6: Uses Windows Data Protection API (DPAPI) encryption
    • Manual configuration, fewer automation features

Both versions store connection strings encrypted — you enter unencrypted values, the system encrypts automatically.

→ Configuration Changes shows all differences in detail

Databases Affected

This guide covers migration of:

Estimated Time & Downtime

Migration Type Planning Time Service Downtime Total Duration
Local Disk Move 1-2 hours 30-60 minutes 2-3 hours
Remote SQL Instance Move (same server) 2-4 hours 1-2 hours 4-6 hours
Remote SQL Instance Move (different server) 4-8 hours 2-4 hours 6-12 hours
SQL Server Version Upgrade 6-12 hours 2-4 hours 8-16 hours

Times vary based on database size, network speed, and team experience.

Best Practices

✅ Always Plan First — Never rush into migration without a clear plan
✅ Test in Staging — Validate the process in a non-production environment
✅ Backup Everything — Full backup before any migration
✅ Notify Stakeholders — Inform users about planned downtime
✅ Have a Rollback Plan — Know how to revert if issues occur
✅ Monitor After Migration — Watch for issues in the first 24-48 hours
✅ Document Changes — Keep records of what was moved and when

Next Step

Ready to start? Choose your migration path: