I´m Reading the Upgrading from Microsoft Dynamics NAV 3.70 to Microsoft Dynamics NAV 2009 SP1.doc.
But i have a database Dynamics (native) NAV3.7A and i want to migrate to SQL.
I read the Microsoft Dynamics® NAV Upgrade Toolkit.pdf and on the page 2 i see this:
The Upgrade Toolkit also contains the tools for migrating from Microsoft Dynamics NAV 2009 to Microsoft Dynamics NAV 2009 with Microsoft SQL Server and a description of the procedures involved. Upgrading to Microsoft Dynamics NAV 2009 is the first step in the process of migrating to the SQL Server option for 2009. For more information, see Chapter 5.
My question is:
I have to migrate from 3.7A to 2009 R2(native) and them migrate this to 2009 R2 (SQL)?
I am not sure about version 3.7, but in the newer versions, you can take a backup from the native db and restore it on to a SQL db, using nav native and nav SQL clients.
The SQL migration from Native can happen at any time before the upgrade or after the upgrade. As above user mentioned the process can be as easy as backup and restore. The issue is Date field.
In sql server dates cannot be older than a 1500. In Native they can go to 1/1/0001. So you will need to fix those dates. There is a codeunit that will automatically check all the fields. That's chapter 5.
Ahmed Rashed Amini
Independent Consultant/Developer
Comments
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
But i have a database Dynamics (native) NAV3.7A and i want to migrate to SQL.
I read the Microsoft Dynamics® NAV Upgrade Toolkit.pdf and on the page 2 i see this:
The Upgrade Toolkit also contains the tools for migrating from Microsoft Dynamics NAV 2009 to Microsoft Dynamics NAV 2009 with Microsoft SQL Server and a description of the procedures involved. Upgrading to Microsoft Dynamics NAV 2009 is the first step in the process of migrating to the SQL Server option for 2009. For more information, see Chapter 5.
My question is:
I have to migrate from 3.7A to 2009 R2(native) and them migrate this to 2009 R2 (SQL)?
In sql server dates cannot be older than a 1500. In Native they can go to 1/1/0001. So you will need to fix those dates. There is a codeunit that will automatically check all the fields. That's chapter 5.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n