Why is retrieving data on the new server slower than on the old one?

Torquinian 1 Reputation point
2025-01-22T16:36:52.1333333+00:00

I have customer with Application and Data Servers. Users access the Application Server which obtains the data from the Data Server. Recently, a new Application Server was introduced to replace the original.

The old Server was a Windows Server 2008 R2 Standard SP1. The new Server is a Windows Server 2019 Standard.

The access speeds using the new Server are noticeably slower than when using the old Server, especially when thousands of rows are being returned. The Data Server is now in the same building (It was not before). The cabling and switches are now all high speed (They were not before).

My thoughts are turning to the Drivers on the new Server being slower in some way to those on the old server.

The old Server had the MS SQL Server 2008 R2 and the Native Client drivers, as well as the 2012 Native Client. The new Server has two MS ODBC Drivers (Version 11 & 13 - Old, I know) and the 2012 Native Client.

I would have thought that the 2012 Native Client would have kept the speed to at least the same level as before, but obviously not.

The old Application Server has a Xeon E5620 @2.40 GHz, with 32GB memory and is 64 bit. The new Application Server has a Xeon Silver 4114 @2.20 GHz, with 128GB memory and is 64 bit OS and processor.

The Data Server is running SQL Server 10.50.1617.

I know that SQLNCLI is out of date - This is an old system that is being hauled into this century, one piece at a time.

I would appreciate any suggestions as to what might be causing this.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,470 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Erland Sommarskog 116.8K Reputation points MVP
    2025-01-22T22:00:31.16+00:00

    You also need to nail down if specific queries are misbehaving, of there is something general. You said that you saw this with queries that return many rows, but it could also be that these queries are hit by changes in query plans.

    And also, is the bottleneck between SQL Server and the application server or between application server and the client.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.