The Client went live on the 6th. This is the task I told you about in last September.
The database was 567GB in size with just a little less than 400GB used. It had 1.506.747 sales invoices and 30.438.858 value entries. Version 4.0Sp3 with a lot of added fields and customization.
When I first ran the upgrade process with the standard upgrade tool it took about ten days. As you can see there is no way to stop a company for ten days. The process was rewritten and these are the steps I used.
- Backup the live database with compression enabled
- Copy the backup file to the new SQL server
- Restore the backup to the new server
- Drop all statistics that was stopping me from modifying tables
- Run Inventory Adjustment
- Import and execute 4.0 SP3 -> 2009 R2 Step 1
- Import 2009 R2 objects
- Prepare data for Step 2 by importing conversion tables
- Execute 4.0 SP3 -> 2009 R2 Step 2
- Import 2009 R2 -> 2013 R2 upgrade objects and execute Step 1
- Change database compatibility level to 2012
- Execute SQL commands to drop all statistics that was blocking database conversion
- Open the database with NAV 2013 Developement Environment and convert database
- Open the database with NAV 2013 R2 Developement Environment and convert the database
- Compiled the system tables
- Changed the SQL Command Timeout for the service to 12:00:000 and started the service
- Selected “No” in the Developement Environment option “Prevent data loss from table changes”
- Imported all NAV 2013 R2 objects
- From PowerShell, executed Sync-NAVTenant
- Selected “Yes” in the Developement Environment option “Prevent data loss from table changes”
- Import 2009 R2 -> 2013 R2 upgrade objects and execute Step 2
There where a few minor steps in between and after that was needed for this customer but basically this was it.
The good news is; this was completed in just under 23 hours with an unexpected delay of just over an hour. This can be done and the client is happy.
