My Microsoft Dynamics GP System is Slow – 10 Common SQL Server Performance Issues
The most common issue in our industry Dynamics GP partner hears is performance. Nobody likes it when their Microsoft Dynamics GP system is “slow”.
Usually, the answer to the problem requires an understanding of Microsoft SQL, Microsoft Dynamics GP and the customer’s environment. If you call Microsoft and tell them, “My Dynamics GP system is slow” they are most likely going to tell you to read a white paper on performance issues and follow the 50 or so recommended steps. They hope that you won’t call again because they know it is not an exact science with one clear answer. It is extremely difficult to diagnose a complex problem with very little background information. Slow performance can be caused by so many different issues, sometimes a combination of issues with subtle, nuanced differences.
An experienced Dynamics GP Partner, with expertise in both the financial and technical side of Microsoft Dynamics GP, is much more likely to give you an accurate diagnosis. Our team at Dexpro Dynamics loves this type of challenge. We are like the “Dr. House” of Dynamics GP diagnosis, if you will.
If you tell us that your “Dynamics GP system is slow” we will start by checking the most common causes related to Microsoft SQL Server.
10 SQL Server Points to Check to Improve your Dynamics GP Performance
- Confirm latest SQL service pack is applied.
- Confirm you have sufficient space on C drive, this alone can cause performance problems, especially in VM environment.
- Server hardware should be a least a quad processor with 16-32GB memory. Note: This gets very client specific. It is best to observe the performance of the server.
- Shrink database jobs are considered a bad practice for Dynamics GP databases and we do not recommend doing this.
- Confirm database maintenance plans are scheduled (excluding shrink).
- Check SQL Jobs for errors or for jobs known to cause issues.
- DBCC checkdb and DBCC checkcatalog should zero issues.
- Dynamics GP database owner should be DYNSA and each database should match SQL version.
- Management Reporter can be very resource hungry application. Best if it doesn reside on SQL server.
- Remember that SQL Server 2012 and above allocates memory differently than SQL 2008 and if other applications are on the same server it may need to be capped at 75%-85%. If none of these points solves the issue, we will move on to another set up of best practices.
As an introduction to our business, we offer one free 30-minute consultation to our new clients.
We are a Dynamics GP partner with a strong focus and skillset on the technical side with several of our team members being experienced SQL DBAs and IT professionals. If your Dynamics GP system is running slow or if you have encountered an issue that nobody could resolve, we will either find a solution or let you know where you can turn to get your issue resolved.
Contact us at Dexpro Dynamics at 855-703-4300 or info@dexprodynamics.com.
By Dexpro Dynamics, Microsoft Dynamics GP Silver Competency Partner, www.dexprodynamics.com
