Click here to
Subscribe to
our Newsletter
This is repost of an article I wrote for the Knights of GP Blog. It explains the performance issues with using Microsoft SQL Server 2025 with Microsoft Dynamics GP and how to resolve them.
Here is the link to the original article on the Knights of GP site:
After the release of Microsoft SQL Server 2025, we are now starting to see customer sites implementing the new version in their Microsoft Dynamics GP environments.
So far, I have been notified by two customers, that I work closely with, that they are having issues with Dynamics GP performance being slower on the SQL Server 2025 than their previous SQL Server version.
The following information on the issue and a solution has been provided by my colleague and friend, Arthur Achilleos, with a call out to Rob Farley MVP (who assisted Arthur’s troubleshooting).
I recently had a discussion with a customer about GP Power Tools appearing to slow down Microsoft Dynamics GP performance during login.
In summary, GP Power Tools was not slowing down performance, but it was making users wait until all background login processes had completed before they could use GP. The option to display the “Please Wait” dialog is controlled by a setting in the Administrator Settings window.
Something that is always a question when adding an ISV (Independent Software Vendor) add on product to Microsoft Dynamics GP is whether it negatively affects performance.
The short technical answer is always going to be Yes. As any additional code will take time to process. However, the real question is whether the effect on performance is noticeable to users.
Today, I started the morning with a support call with a US customer and partner regarding what appeared to be a performance issue caused by GP Power Tools.
Once we used GP Power Tools to troubleshoot and identify the root cause of the issue, it was easy to see why they incorrectly thought the problem was caused by GP Power Tools.
Read on to understand what happened and how to make sure it does not happen on your systems ….
A while ago, I wrote a post: Why can’t I run Microsoft Dynamics GP via ODBC over a WAN? which discussed the reasons why Microsoft Dynamics GP will not work well when trying to use an ODBC (Open Data Base Connectivity) connection over a WAN (Wide Area Network). The post mentioned that the only support method for running Microsoft Dynamics GP in a WAN environment was by using Terminal Server.
With Terminal Server and its clients, all the processing is performed on the Terminal Server. The only processing handled on the client is drawing the screen and communicating with the Terminal Server. The communication between the Terminal Server and the client is just the screen data to be displayed and the keyboard and mouse inputs back to the server. If the Terminal Server is slow, processing will be slow and screen refreshing might be affected. If the connection between the Terminal Server and the client is slow, processing will be fast and only the screen refreshing will be slow.
Note: Citrix sits on top of Terminal Server and provides additional functionality. So when Terminal Server is discussed it refers to both Terminal Server with and without Citrix.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I thought I would spend a little time explain how to read a Dexterity Script Profile to resolve a performance issue. To demonstrate this I will use a support case I had where the customer was intermittent long delays when clicking on the checkbox on the Apply Sales Document window.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I have just returned from Microsoft Dynamics Conference 2011 Atlanta conference, and based on the feedback during the sessions that Mariano and I presented as well as comments from the session evaluations, I thought it would be worth discussing some of the common Support Debugging Tool (SDT) myths.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This summer I was contacted by one of my associates in our LATAM office.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
If you have not been keeping track of the blogsphere you might have missed some new whitepapers that have been released….
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I had an interesting support case last week where the partner was asking why running Microsoft Dynamics GP via ODBC over a WAN was so slow? They had already told the customer that this was not supported, but the customer wanted reasons.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
Breaking with my recent series on Smartlist and specifically the Smartlist: Exports slowly to Excel – Part 1 post, a comment and followup question to that post was:
This is great! But is there a similar switch for the Dynamics GP lists such as the “All Sales Transactions” or “Accounts” list?
Good question and honestly I did wonder about that myself. But it was outside my “all things Smartlist” topic so I figured I’d check it out later.
Now that it came up – today looks like “later” so I thought I’d dig into it.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This is the 4th post in a series of Smartlist posts in the last weeks. In these articles, I’ve given answers and solutions to common questions about Smartlist that are typically of the “Why doesn’t Smartlist..?” variety.
Last week, the question we were looking at was:
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
In the last few weeks (here and here), I’ve enumerated several questions that I’ve been asked and have seen posted to the public Dynamics GP newsgroups. These questions are typically of the “Why doesn’t Smartlist..?” variety.
In this post and a few planned future posts, I’ll look at each of these questions individually and give a few thoughts around them and maybe a few solutions as well.
This is a reposting of an article Dave Dusek originally wrote on my Developing for Dynamics GP blog.
This blog post is about a difficult Visual Studio Tools for Microsoft Dynamics GP (VSTools) performance issue that I had on a citrix server environment. What I’m going to do is list the symptoms that I received in the case and then the troubleshooting that we did to narrow down the situation and the results of that. So what the case started with was the following:
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
If you look at a SQL Server installation of Microsoft Dynamics GP, in the Stored Procedures folder underneath the Dynamics system database or a company database you will find a large number of stored procedures starting with the initials”zDP”. This article explains what the zDP stored procedures do and why they exist.