We would like to run an instance of NAS on the SQL Server that holds the NAV database.
Our database is V4, running on SQL 2005.
I do seem to remember from years ago this was not recommended for SQL performance reasons. Is this correct?
I have been searching the knowledgebase for an answer, but can't find anything.
you are right, was not recommended in the past
but look at this post by Alain Krikilion abour NAS for NAV 4 & 5 : How To install a NAV Application Server (NAS)?
my experience for V 4 & SQL 2005: use another server for NAS
> sql performance client is cpu\time consuming
> problems with timezone if you have multi-db regionale & time-zone dependent on same db server
> if NAS crash sometimes is necessary to reebot sql server
Actually it depends on the server specifications and the transaction volume to be processes. If you have sufficient CPU, RAM and DISK a NAS service MIFGT work on the same box. Basically. If you run a 32bit environment you have to be careful, as you might encounter problems with adressing RAM. Even on 64bit systems older NAS run into memory-allocation-problems (WoW Mode).(see Roberto's posting)Thus, to have sufficient fault-tolerance IMO it's wise to have separate machines for SQL and NAS.
We will keep them on different servers - thanks for your help.