Upgrading NAV2009R2 to NAV2016

rsaritzky

Hi all,

I'm looking for the roadmap for upgrading a NAV2009R2 database to NAV2016, and have a couple of issues that I am seeking opinions on. For purposes of discussion, I'm talking only about the DATA upgrade, not the application objects (i.e. pages, reports, codeunits) upgrade.

Question 1:
The UpgradeToolkit directory on the NAV2016 CU2 DVD contains Upgrade700900.US.fob, Upgrade710900.US.fob and Upgrade800900.US.fob. I haven't seen any definitive statement, but I am assuming that I have to upgrade in 2 steps, similar to how is documented in the NAV2009->NAV2015 document, i.e. Upgrade from NAV2009R2 to NAV2013, then from NAV2013 to NAV2016

Question 2:
The database to be upgraded is nearly 400GB. Has anyone seen recommendations for the best hardware environment for doing the upgrade? I have seen comments around to do everything on a single box (i.e. application and SQL Server), with locally-attached storage. Any opinions here? What about SSD drives vs. regular hard drives? We have an enterprise-server-class environment, so I just need to tell our IT manager what we need.

Question 3:
Based on various comments, particularly about the Dimension-Ledger upgrade step, I was thinking about doing a "first-pass" data upgrade on a database with much of the history deleted and/or compressed, then do the "real" test upgrade. The reasoning here is to encounter any errors more quickly and be able to resolve them before embarking on a "many hour" upgrade.

Question 4:
The Change Log Entry table in our current database is about 60GB. Other than the physical disk space, is there any impact on leaving this table in-place? I do have the potential option of archiving 90% the Change Log entries into another table, or another separate database if necessary.

Thanks to everyone

Ron

postsaurav

Hi,

I Hope Below Answers Should Help -

Question 1 - Yes it will be a Two Step Process.

Question 2 - As per my understanding -
> Do it all on same Server.
> Drive Should Not be Network Drives.
> Storage Should be Locally Attached.

Question 3 -
To Identify Dimension Error Refer Article Below, This will give you the Dimension List which have been deleted.
You Need to Create these dimension Values in the Current 2009 System.

http://saurav-nav.blogspot.in/2014/05/nav-2013-nav-2013-r2-conman-issue.html

To Add one More Point (as you are coming from NAV 2009) -

> You Might have issues related to Line Feed and Charcter Feed in NAV 2009 Data. Refer Link For How to Resolve before start Migration Process.

http://mibuso.com/downloads/nav-classic-upgrade-identify-special-character-sql-query

Question 4 -
The Correct way to do is -
1> Create a Seprate Database on SQL (Same Collation).
2> Using Create To for Change Log Entry Table, create Change Log Entries Table in the New Database.
3> Transfer Data To a Diffrent SQL Database using SQL Data Transfer Wizard.
4> Once Upgrade is Over Transfer Data to NAV Custom Table Say 50001 having Structure as Old Change Log Entry (2009).
5> Create a Custom Codeunit to Update & Transfer Only Change Log Entries from Custom Table to New Standard Table.

For Data Migration Steps From 2013 / 2013 R2 / 2015 TO NAV 2016 Refer Here -
http://saurav-nav.blogspot.com/2015/10/microsoft-dynamics-nav-2016-data.html

let me know if any doubts

postsaurav

Hi,

I Hope Below Answers Should Help -

Question 1 - Yes it will be a Two Step Process.

Question 2 - As per my understanding -
> Do it all on same Server.
> Drive Should Not be Network Drives.
> Storage Should be Locally Attached.

Question 3 -
To Identify Dimension Error Refer Article Below, This will give you the Dimension List which have been deleted.
You Need to Create these dimension Values in the Current 2009 System.

http://saurav-nav.blogspot.in/2014/05/nav-2013-nav-2013-r2-conman-issue.html

To Add one More Point (as you are coming from NAV 2009) -

> You Might have issues related to Line Feed and Charcter Feed in NAV 2009 Data. Refer Link For How to Resolve before start Migration Process.

http://mibuso.com/downloads/nav-classic-upgrade-identify-special-character-sql-query

Question 4 -
The Correct way to do is -
1> Create a Seprate Database on SQL (Same Collation).
2> Using Create To for Change Log Entry Table, create Change Log Entries Table in the New Database.
3> Transfer Data To a Diffrent SQL Database using SQL Data Transfer Wizard.
4> Once Upgrade is Over Transfer Data to NAV Custom Table Say 50001 having Structure as Old Change Log Entry (2009).
5> Create a Custom Codeunit to Update & Transfer Only Change Log Entries from Custom Table to New Standard Table.

For Data Migration Steps From 2013 / 2013 R2 / 2015 TO NAV 2016 Refer Here -
http://saurav-nav.blogspot.com/2015/10/microsoft-dynamics-nav-2016-data.html

let me know if any doubts

rsaritzky

Thanks, Saurav for the suggestions.

Ron