Navision 3.60 Database upgrade to Navision 4.03 MSSQL 2005.

tekati

from:
Navision Client 3.60
Navision DB 3.60
Native Navision DB
to:
Navision Client 4.03
Navision DB 3.60
MS SQL 2005

We are working with our partners to discuss this and this is what they have suggested. I would like to get other peoples comments and suggestions on whether this is a good move and what all it really takes to get this job done.

Our partner wants to charge us a substantial amount of money to do this job. 26-32 hours. Now if we were upgrading the DB to 4.XX I could see some extra time for that but we would be sticking with 3.60 according to our partner and just using the 4.03 client.

From my understanding so far it basically goes something like this. You make a backup copy of the working DB which by the way is at 9GB as of now so should be around 3GB as a backup. Then you have to run some tool that fixes dates that ARE an issue coming in to the SQL DB. Then you basically install the Navision 4.03 SQL client and import the data in to SQL and upgrade everyones client to the 4.03 SQL version and you are ready to roll.

My question is besides looking at the tool that fixes the dates run which I can see running for some time what in the world there will take 26-32 hours to accomplish?

Unless I am really missing some stuff.

If I am missing some stuff can someone point me in the right direction on a howto or some method of doing this work? I would really like to do it myself. I have spoken with someone from the forums that wants to work with us and I am looking forward to that relationship but time for that person is limited at the present and I would actually not mind trying to learn by doing something like this anyway.

We have reasons for switching to MS SQL before people start hammering me with WHY WOULD YOU DO THAT questions.

Ian_Piddington10199

It doesn't sound entirely unreasonable to me. I would expect that they would do a test conversion prior to converting your live data base. They should be checking that things still work after the move to SQL. For instance the way sorting works in the C/Side database is different to the SQL database, so they need to be checking that routines that sort and filter data are still working correctly. They are very likely to be doing some optimisation for SQL so that performance isn't adversely effected. If the solution is customised they may be checking that the code won't 'break' SQL and perform badly.

There are quite a few considerations to moving between the 2 platforms, so less than a week’s work for the Partner is pretty good going i think. I haven't done any migrations between the 2 platforms for a while but I recall the last time i worked on one it took a bit longer than 32 hours.

Ian

bbrown

On of our cleints just went thru this exact conversion process. They moved from 3.60 native to SQL 2005 with 4.03 clients and the 3.60 database. They did a large part of the work themselves and used us to perform task that required a full developers license and for technical advice. There were a number of things that did not work correctly under SQL and performance required major work. Even though they did a lot of work themselves they still used a large amount of time from us. (Well above the 26-32 hours you have been quoted.