- 2 minutes to read
Local Disk Move
If you intend to move the Nodinite databases to other disk volumes on the same SQL Server instance, follow the quick guide below:
Quick Reference
- Stop Nodinite applications and services
- Detach databases to be moved (with drop existing connections options set). Make sure to read the Microsoft Database Detach and Attach (SQL Server) user guide first
- Move the database files locally to the new destination
- Attach the databases
- Review the default paths for Data and Log files
- Restart services
Visual Overview
graph LR
subgraph "After"
roSQL2[fal:fa-database SQL Server instance]
roD2[fal:fa-hard-drive M:\ DATA]
roE2[fal:fa-hard-drive N:\ LOG]
roSQL2 --> roD2
roSQL2 --> roE2
end
subgraph "Before"
roSQL[fal:fa-database SQL Server instance]
roD[fal:fa-hard-drive D:\ DATA]
roE[fal:fa-hard-drive E:\ LOG]
roSQL --> roD
roSQL --> roE
end
Above is an example of a local move from one set of disks to another.
Review Default Paths for Data and Log Files (Advanced Disk Schemes Only)
This step applies ONLY if you are using an advanced rotating disk scheme with the LogLocations system parameter.
On the new SQL Server instance(s), you might be using other default disk volumes compared to the old environment.
IF you have configured multiple disk volumes using the advanced disk scheme:
- Nodinite 7: Update the System Parameter - LogLocations to reflect the new disk volumes and file paths
- Nodinite 6: Update the System Parameter - IMLogLocations to reflect the new disk volumes and file paths
Refer to the LogLocations documentation for detailed configuration examples and best practices.
Next Step
Migration 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
- Remote SQL Instance Move - For different SQL Server
- Validation and DACPAC Registration - Testing and verification
- Post-Migration Steps - Cleanup and optimization