Migration from SQL Server from 2000 to 2005 2008 (Nav 3.70B)

DyNav4

Hello,

i am supervising a customer who uses Navision 3.70B but without product support.

Currently SQL 2000 with the latest SP's is running under Windows Server 2003.

They plan to upgrade the hardware, think about upgrading the SQL Server too.

Are there any problems to expect?

Ok, i know, the best would be to sell a maintainance agreement and install a technical upgrade, but first step should be - if possible - to make an SQL upgrade only.

Peter

garak

1.) 3.70 is not supported on 2005 / 2008.
2.) for 2005 u need min. 4.0 SP1.
3.) You can upgrade the executables of the NAV directory (run a 3.70 database (objects) on 4.0 SP3 technology).
4.) Why not also upgrade the exe to 5.00 SP1 or 4.03 with last HF?
5.) before upgrade of the exe, test your database on a testsystem for perfomance. With 4.0 some new commands and "features" like indexhint was released. Also read the perfomance subforum. with 4.03 u must also set a traceflag on the SQL Server.

Regards

kine

garak wrote:

1.)
4.) Why not also upgrade the exe to 5.00 SP1 or 4.03 with last HF?

without product support.
...

Ok, i know, the best would be to sell a maintainance agreement and install a technical upgrade, but first step should be - if possible - to make an SQL upgrade only.

;-)

Yes, this is a problem, because without special changes the nav 3.70 will not work with SQL 2005 or 2008. If you will try it and you will make it running, you need to be prepared for other technical issues which can happen...

DenSter

You can't do a SQL Server upgrade to 2005 or 2008 for a customer that is on 3.7, because it was never made to work on those versions. I am sure there are people that have got it working, but I would never advise my customer to go that route, because it is a game of Russian Roulette until problems start happening. For enterprise mission critical information systems you do not want to be on any unsupported versions of software.