NAV server using all available RAM - 2015

Rodtmclean

Hi,

A client is having an issue whereby all the memory is being consumed by the NAV server (Microsoft.Dynamics.Nav.Server.Exe) periodically. This doesn't seem to be connected to a particular report/process though we are making heavy use of the job queue including exporting via an XMLport.

Has anyone experienced a similar issue?

Thanks
Roddy McLean

bbrown

What version of NAV? If 2013 or above, the NAV server is a 64 bit service and thus able to use all the memory available. Microsoft did tell me that it has a hard limit of 250 GB. How much memory it does use is greatly dependent on what is being done. How much memory are we talking about?

Rodtmclean

Hi,

They are on 2015 and will get a platform upgrade to cumulative upgrade 6 at the end of this week. Its basically using all RAM 16GB (steals it from SQL also). SQL server is running on the same server :!:

Regards
Roddy

bbrown

Rodtmclean wrote:

Hi,

... SQL server is running on the same server :!:

Regards
Roddy

Really BAD idea!!!

Rodtmclean

Thanks for the reply ,

I've involved Microsoft (at the bequest of my company) and if Msoft indicate this, then putting SQL on a different server will be my recommendation. Can you expand on the reasons this is bad please?

(I have one myself, NAV can steal memory from SQL, on SQL minumum RAM is set to 0 and Max is 4096MB).

It is the NAV service that is consuming RAM though and that will hurt SQL also.

Regards
Roddy

bbrown

Be sure you are speaking with the right group at MS. The group I'd suggest is the Partner Technical Advisory Service.

BTW - I posed this question of when would it be acceptable to run SQL and the NAV Service on the same server back when RTC first came out. Their reply was NEVER. I doubt that has changed. That is the #1 reason for not doing it.

Rodtmclean

Thanks Bbrown,

Can I ask, was it Microsoft that said never run SQL and NAV on the same server or a MVP/Mibuso expert?

Just curious.

Much appreciated and thanks
Roddy

bbrown

It was the "Partner Technical Advisory Service" at Microsoft. I will try to find that email later if I can an post their response.

Rodtmclean

Thanks again

Roddy

bbrown

I found that email.

Here is the question I asked:

At what system size would you recommend separating the NAV server (service) from the SQL Server? Should it be on a dedicated system?

Here is the response from Microsoft:

I would never run the service tier and SQL on the same box. A SQL Server should be a SQL server and nothing else.

With NAV 2013 and up, I'd also say that the NAV Service should be its own box and nothing else.

Rodtmclean

Thanks BBrown,

This is pretty much what I'm getting from Microsoft.

I'm wondering why hardware requirements given by Microsoft (NAV documentation) for 2013/2015 are so low? It would do us all a favor if they updated them to something more realistic, like what is indicated by yourself. They should also just specify that SQL should be on its own box all the time.

Thanks again!
Roddy

bbrown

Rodtmclean wrote:

Thanks BBrown,

This is pretty much what I'm getting from Microsoft.

I'm wondering why hardware requirements given by Microsoft (NAV documentation) for 2013/2015 are so low? It would do us all a favor if they updated them to something more realistic, like what is indicated by yourself. They should also just specify that SQL should be on its own box all the time.

Thanks again!
Roddy

The requirements published by Microsoft (and many other software vendors) are minimum specifications. They are not what it takes to run the product in the real world.