4.0 and 2009 databases coexisting on the same server

AlexWiley

Hi everyone, we have our 64bit SQL 2005 servers running our 4.0 Prod and Dev environments. As anyone run into any issues installing the 2009 database and components on the same servers running a 4.0 db?

Alex_Chow

It shouldn't be a problem. We have different versions running on our SQL box at our company without any problems.

ara3n

The only component on sql server that needs to be installed is xp_ndo_64.dll. This is used for windows authenication only. This dll is backward compatible with older version.
What else are you trying to install on the server?

garak

There is no problem. and like ara3n said. U need only to install the xp_ndo-64.dll.

But you shuld be carefully on the client site. In a bad situation a user can open and convert the 4.0 database with the Classic 2009 Client. That could be the only problem.
Or did u use only the Classic 2009 Client?

AlexWiley

Nothing else is going on the server and to start out with only a couple people are going to have access to it. The purpose is to transition from 4.0 to 2009, so when the clients change they will change for everyone. I will make sure the non-Navision IT people are aware of that though garak. Thanks for the responses everyone, I always appreciate peace of mind!

kine

I see one possible problem - license, which is not "per database" enabled. If you are using partner's license, no problem, if you are using customer's license, it could be problem...

kriki

garak wrote:

But you shuld be carefully on the client site. In a bad situation a user can open and convert the 4.0 database with the Classic 2009 Client. That could be the only problem.

Best way to avoid this problem is to create shortcuts with the connection parameters for each DB and that point to different zup-files. So you can always use these shortcuts to open the DB.

garak

Right.