We have a new client that is now running Nav 2013, since the beginning of March.
Basic installation, only 4 users, almost no customization done to the database.
They have been complaining about performance issue for the past 2 weeks.
The system is slow in the morning, gets better in the afternoon and start to slow down again at the end of the day.
I'm far from a SQL/Server expert and I have no idea what to look at.
I have started the performance monitor on their server but I'm not sure what I should be monitoring.
What should I look at to try and find why the system is being slow and what needs to be done to improve performance?
0
Comments
The cheapest & most efficient performance upgrade is always the hardware upgrade.
Hardly.
RAM
Disks
Operating system version
SQL Server Version
Database size
number of databases
http://mibuso.com/blogs/davidmachanick/
But hardware is only 1 part of the performance puzzle.
info on disk (for each physically separate array:
Number, size, and type of disk
RAID level
WHat is array used for?
We gave the client the system requirements for Microsoft Dynamics Nav Server and it's one of the O/S listed on that list.
They already had a license for that O/S so they selected this one.
As for the disk, I do not have the information.
I will ask them and get back to you.
Anything else I should be looking at while I wait for their answer?
Also confirm that the login account for the SQL server engine has been granted the "Lock Pages in Memory" right.
With such a tiny database and few users, it's doubtful that hardware is a major issue. You could probably run this on a laptop. However, your description of preformance worsening and improving over the course of the day has me thinking about memory paging. That's why my questions above. You don't want memory paging on a SQL box. It just kills performance.
1 - 74.9 GB capacity, 44.48 GB available (O/S and a few programs installed)
2 - 100GB capacity, 96.91 GB available (Database)
3 - 100GB capacity, 99.25 GB available (Backups)
On SQL
Min memory is set at 0
Max memory is set at 2147483647
As for the "lock pages in memory", I'm not familiar with this.
I went to the local group policy editor and looked at the security settings for "Lock pages in memory" and no user has been assigned there.
Is this what you are talking about? If so, which users should be added? If not, where should I be looking?
Also, by looking at the help on SQL Server Management for "Lock Pages in Memory", it says that "Locking pages in memory is not required on 64-bit operating system" and they are on 64-bit O/S
The max memory should be set to something below the physical memory on the server. Also allow for the O/S requirements plus anything else on the server.
That "lock pages in memory" settign is what I am referrign to. The account that is runnign the SQL service should have it granted.
Are the virtual disk, thick or thin partitioned?
We normally just handle the programming/customization of Navision and the client is responsible of the hardware/security/configuration of their server.
So all this is like "Chinese" for me.
The specification I gave you is for the virtual machine. I do not have access to the host.
I was just trying to help the client to see if this is something we could find and fix easily before referring them to a hardware specialist.
Since you are running under VMware, you should find a VMware specialist who understands SQL Server and transaction processing.
It is hard to mess up a 4 user system. Your VMware people have nevertheless accomplished the job.
http://mibuso.com/blogs/davidmachanick/
That setting is actually 2TB. The default max memory setting.
It does seem like a vmware setup issue.
http://mibuso.com/blogs/davidmachanick/
No, actually you're right on target. SQL, and many other 64 bit applications, don't distinquish between physical and virtual memory (think paging file). That default setting tells SQL that it's allowed to use up to 2 TB of memory. The fact that the server only has 8 GB does not matter to SQL. It will just use virtual memory (paging file) to satify its needs. However, since that virtual memory it actually a disk file, in can be rather slow. The need for SQL to constantly page memory can have a performance impact.
Not saying this is the only issue. Or even the major one. Just it's soemthing that sticks out to me based on the info provided so far.
Where are the log files? :-k
I'm betting this whole machine is on a single physical array. So does the log location really matter?