-
Hello, I made performance tests for SQL server 2014 and 2019 on the same environment. I have good results for 2014 and low numbers for SQL server 2019. Are there special settings or this version is not supported yet? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Hi, yes SQL Server 2019 has been tested for the next version, there are no special settings and it works with the current version. You need to provide much greater detail to help diagnose an issue. For example you don't say what workload you are running TPC-C or TPC-H? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
The first reaction is that these numbers are relatively quite low - a simple test with SQL 2019 on an far from state of the art dev PC gives me 150134 NOPM from 345996 TPM. So the first step would be use SSMS Activity Monitor and identify the highest resource wait. IO for logging is often a bottleneck but clearly there is a dependency on the CPU resource as well. |
Beta Was this translation helpful? Give feedback.
-
Closed no further update |
Beta Was this translation helpful? Give feedback.
The first reaction is that these numbers are relatively quite low - a simple test with SQL 2019 on an far from state of the art dev PC gives me 150134 NOPM from 345996 TPM. So the first step would be use SSMS Activity Monitor and identify the highest resource wait. IO for logging is often a bottleneck but clearly there is a dependency on the CPU resource as well.
Also is this using the same version of HammerDB for both tests?- ie you are currently testing both database versions at the same time with the same stack? - if not what are the versions and are they both running on Windows with the same ODBC client library?