We upgraded from GP2015 to GP2018 R2 and moved to a VMware two VM's one is Server 2019 w/SQL 2019 the other is Server 2016 with RDP and GP 2018.
The servers have plenty of resources available even during the processing.
We upgraded from GP2015 to GP2018 R2 and moved to a VMware two VM's one is Server 2019 w/SQL 2019 the other is Server 2016 with RDP and GP 2018.
The servers have plenty of resources available even during the processing.
Hello CSS,
This could cause some issues, but I would still start with testing on the SQL server to give you a good baseline for performance.
You wouldn't want to spend a ton of time fiddling with SQL settings if the issue is a ethernet cable loose!
Poking around i noticed the SQL compatibility level is 110 SQL 2012. I have seen a couple of docs which suggest GP 2018 compatibility should be a minimum of 130. Any idea if this would be impacting performance.
Agree with Justin,
HW should be ruled out before you try to look at the SQL side in terms of poor performance.
Make sure the VM's are provisioned with plenty of resources (SQL loves to get more RAM, typically 12-16GB should be fine for a couple GP companies and low number of GP sessions (up to 50))
Also rule out poor setup disk sub-systems, as they can be a slow-down factor too.
How was the GP 2015 setup before the upgrade ? pyhsical boxes or virtual platform too ?
You will want to test directly on the SQL server to rule out any network issues.
Where are these physical hosts? Are they are on the same rack?
Thanks!
Sorry it is GP v18.2 (2019). The GP Client is on one VM Server 2016 and SQL is on another VM and the VM's are on different physical hosts
Hello CSS,
First off, it is important to note that SQL 2019 is not supported on any version of GP 2018. It is only supported on GP 18.2 or newer. This is outlined on the system requirements here:
mbs.microsoft.com/.../MDGP2018_System_Requirements
Next, where are you testing speed? Are you testing directly on the SQL Server, or are you testing on another VM? I ask this as a good 90% of performance issues come down to a dodgy connection between the GP Client and the SQL Server.
I would start with testing directly on the SQL Server and reviewing this article and the WhitePaper it links to:
community.dynamics.com/.../performance-with-dynamics-gp-where-do-i-start
André Arnaud de Cal...
292,516
Super User 2025 Season 1
Martin Dráb
231,430
Most Valuable Professional
nmaenpaa
101,156