Upgrade from 4.03 to 2009 to 2013

ajayjain

Hi,

Currently we are on 4.03 SQL 2005 (which was upgraded from 3.7)
heavely customised, 300+ users, 60GB database, 32bit server.

We have plan to upgrade to 2013 next year but we have to immediately move to 2009
as we cannot buy more objects and users on 4.03 and MS has forced to upgrade to 2013

I am planning to convert the same database into 2009 application so everything can be done in few hours
so it will not be an upgrade.

Should I upgrade SQL as well, if so should it be 2008 or 2012

Upgrade to 2013 will be an actual upgrade with SQL as well.

Any complications in converting 4.03 to 2009 and same database to upgrade to 2013

Please advise.


Thanks

Marije_Brummel

Sounds to me you want to do a technical upgrade to 2013. That is not possible.

The highest you can go with classic client is 2009 R2.

If you stay on classic with 2009 R2 it is not necessary to upgrade SQL. SQL2005 is supported until 2015 or 2016.

ajayjain

Hi Mark,

Thanks for your reply
I know we don't have classic after 2009 R2, we will upgrade to 2013 RTC
but I currently need advice only on 4.03 to 2009R2 (classic), yes technical upgrade this stage.
I got 3 questions:

1)
Should I convert the database into 2009R2 (open with 2009 application)
OR should I backup and restore into 2009R2
what will be the difference between the above 2 process.

2) any complications in step 1, it looks like straight forward job, can be done in few hours.

3) doing the step 1 will not cause any issue when we upgrade to 2013


Thanks

Marije_Brummel

The difference between opening the database and converting vs. backup/restore is that in the latter scenario you loose all SQL changes, and end up with a new SQL database.

I try to avoid that and open the database with the client and let it convert. I keep all my fill factors, stored procedures, views, maintenance plans etc.

pdj

(deleted...)

ajayjain

I have done a trial run on test database, upgraded 4.03 to 2009
got 2 errors

you do not have permission to read 'record link' table
same for 'Property Store' table

we are not using these table in database

Marije_Brummel

Have you requested a refreshed license for the new version?

ajayjain

Yes we got new license, everything works fine during a quick test.
i have checked business notification, recordlink table, codeunit 1
I have done user sync as well.
and I tested i did not get any error.

We are live on sql 2005 on 32bit and i upgraded my test on SQL 2008 64 bit
that should not cause any issue.

will dig some more, may be i need to add more permission for normal users on 2009
as record link is not in version 4.