Queries have been running really slowly since upgrading the database to SQL Server 2025.

Question

Queries have been running really slowly since upgrading the database to SQL Server 2025.

Amin 10

After upgrading my SQL Server from versions 2014 and 2022 to 2025, the queries have become noticeably slower.

Viorel 126.8K Reputation points

2025-11-23T10:03:13.5466667+00:00

Is it a query that does not return many results?
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2025-11-23T18:33:32.93+00:00
Did you also change the compatibility level from 120 to 170?

A good way to handle issues like this:

Keep compat level to 120.

Enable Query Store.

Run with compat level 120 a week or two.

Flip to 170.

You can now use Query Store to find regressed queries. and as a quick solution you can force the old plan.

You can also use the Tasks context menu for the database. At the bottom of the menu, you find Database Upgrade which helps you with the steps I outlined above.
Amin 10 Reputation points

2025-11-25T07:54:15.1766667+00:00

I noticed that when I use SQL Server Authentication, this problem occurs. When I add Trusted_Connection=True, the queries run normally; otherwise, they become really slow.
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2025-11-25T21:33:58.62+00:00

While that is a hint, it is not sufficient to tell you what the issue is. It could be that there is an issue with SQL logins in SQL 2025, but I find it more likely that is a performance issue related to row-level security or similar.

You need to track down which queries that actually are slow.
Amin 10 Reputation points

2025-11-27T07:55:11.09+00:00

Everything was working fine with SQL Server 2022 (Windows or SQL Authentication mode), but this problem just happened in SQL Server 2025 using SQL Authentication mode!
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2025-11-27T20:45:56.0166667+00:00

Do you want help with this, or do you only want to make a statement? If you only want to make a statement, we can stop here. If you want help, you need to help us to help you. Can you give an example of a query that is slow with SQL authentication, but runs quickly with Windows authentication?
Akhil Gajavelly 1,810 Reputation points Microsoft External Staff Moderator

2026-01-07T05:17:02.04+00:00
Hi @Amin ,

Thanks for the additional details. At this stage, @Erland Sommarskog have already covered the likely causes and the correct troubleshooting direction.

The difference between SQL Authentication and Windows Authentication by itself isn’t enough to diagnose the issue. To move this forward, we’ll need something concrete to compare specifically.

A sample query that is slow when executed using SQL Authentication

The same query running fast with Windows Authentication

Ideally, the execution plans (or Query Store plans) for both runs

Without a query and plan comparison, it’s not possible to determine whether this is related to SET options, security context (such as RLS or permissions), or plan caching behaviour in SQL Server 2025.

Once that information is available, the root cause should be straightforward to identify.

Thanks,
Akhil.
Akhil Gajavelly 1,810 Reputation points Microsoft External Staff Moderator

2026-01-07T05:19:30.6666667+00:00
Hi @Amin ,

Thanks for the additional details. At this stage, @Erland Sommarskog have already covered the likely causes and the correct troubleshooting direction.

The difference between SQL Authentication and Windows Authentication by itself isn’t enough to diagnose the issue. To move this forward, we’ll need something concrete to compare specifically.

A sample query that is slow when executed using SQL Authentication

The same query running fast with Windows Authentication

Ideally, the execution plans (or Query Store plans) for both runs

Without a query and plan comparison, it’s not possible to determine whether this is related to SET options, security context (such as RLS or permissions), or plan caching behavior in SQL Server 2025.

Once that information is available, the root cause should be straightforward to identify.

Thanks,
Akhil.
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2026-03-18T21:23:13.7+00:00
Luca Domenichini, for more discussion on the effects of PBKDF2, see the thread https://learn.microsoft.com/en-us/answers/questions/5662030/sql-server-2025-executing-request-with-in-sql-conn.

Short story: It's a only a problem if:

You use SQL authentication.

You run many short requests.

You have turned off connection pooling.

All three are dubious practices, particularly the latter two.
Akhil Gajavelly 1,810 Reputation points Microsoft External Staff Moderator

2026-04-01T06:39:42.27+00:00

Hi @Amin,

Just checking in were you able to review the guidance regarding PBKDF2 impact and connection behavior?

As mentioned, the issue typically only surfaces when using SQL authentication with many short requests and connection pooling disabled. If you’re still experiencing the problem, please share your current setup and observations so we can help further.

Thanks,
Akhil.

Answer recommended by moderator

1 additional answer

Your answer

Viorel 126.8K Reputation points

2025-11-23T10:03:13.5466667+00:00

Is it a query that does not return many results?
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2025-11-23T18:33:32.93+00:00

Did you also change the compatibility level from 120 to 170?

A good way to handle issues like this:

Keep compat level to 120.

Enable Query Store.

Run with compat level 120 a week or two.

Flip to 170.

You can now use Query Store to find regressed queries. and as a quick solution you can force the old plan.

You can also use the Tasks context menu for the database. At the bottom of the menu, you find Database Upgrade which helps you with the steps I outlined above.
Amin 10 Reputation points

2025-11-25T07:54:15.1766667+00:00

I noticed that when I use SQL Server Authentication, this problem occurs. When I add Trusted_Connection=True, the queries run normally; otherwise, they become really slow.
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2025-11-25T21:33:58.62+00:00

While that is a hint, it is not sufficient to tell you what the issue is. It could be that there is an issue with SQL logins in SQL 2025, but I find it more likely that is a performance issue related to row-level security or similar.

You need to track down which queries that actually are slow.
Amin 10 Reputation points

2025-11-27T07:55:11.09+00:00

Everything was working fine with SQL Server 2022 (Windows or SQL Authentication mode), but this problem just happened in SQL Server 2025 using SQL Authentication mode!
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2025-11-27T20:45:56.0166667+00:00

Do you want help with this, or do you only want to make a statement? If you only want to make a statement, we can stop here. If you want help, you need to help us to help you. Can you give an example of a query that is slow with SQL authentication, but runs quickly with Windows authentication?
Akhil Gajavelly 1,810 Reputation points Microsoft External Staff Moderator

2026-01-07T05:17:02.04+00:00

Hi @Amin ,

Thanks for the additional details. At this stage, @Erland Sommarskog have already covered the likely causes and the correct troubleshooting direction.

The difference between SQL Authentication and Windows Authentication by itself isn’t enough to diagnose the issue. To move this forward, we’ll need something concrete to compare specifically.

A sample query that is slow when executed using SQL Authentication

The same query running fast with Windows Authentication

Ideally, the execution plans (or Query Store plans) for both runs

Without a query and plan comparison, it’s not possible to determine whether this is related to SET options, security context (such as RLS or permissions), or plan caching behaviour in SQL Server 2025.

Once that information is available, the root cause should be straightforward to identify.

Thanks,
Akhil.
Akhil Gajavelly 1,810 Reputation points Microsoft External Staff Moderator

2026-01-07T05:19:30.6666667+00:00

Hi @Amin ,

Thanks for the additional details. At this stage, @Erland Sommarskog have already covered the likely causes and the correct troubleshooting direction.

The difference between SQL Authentication and Windows Authentication by itself isn’t enough to diagnose the issue. To move this forward, we’ll need something concrete to compare specifically.

A sample query that is slow when executed using SQL Authentication

The same query running fast with Windows Authentication

Ideally, the execution plans (or Query Store plans) for both runs

Without a query and plan comparison, it’s not possible to determine whether this is related to SET options, security context (such as RLS or permissions), or plan caching behavior in SQL Server 2025.

Once that information is available, the root cause should be straightforward to identify.

Thanks,
Akhil.
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2026-03-18T21:23:13.7+00:00

Luca Domenichini, for more discussion on the effects of PBKDF2, see the thread https://learn.microsoft.com/en-us/answers/questions/5662030/sql-server-2025-executing-request-with-in-sql-conn.

Short story: It's a only a problem if:

You use SQL authentication.

You run many short requests.

You have turned off connection pooling.

All three are dubious practices, particularly the latter two.
Akhil Gajavelly 1,810 Reputation points Microsoft External Staff Moderator

2026-04-01T06:39:42.27+00:00

Hi @Amin,

Just checking in were you able to review the guidance regarding PBKDF2 impact and connection behavior?

As mentioned, the issue typically only surfaces when using SQL authentication with many short requests and connection pooling disabled. If you’re still experiencing the problem, please share your current setup and observations so we can help further.

Thanks,
Akhil.

Answer 1

Luca Domenichini 0

We are experiencing the same issue. Login latency is very noticeable.
Seen this on MS Learn:
https://learn.microsoft.com/en-us/sql/sql-server/sql-server-2025-known-issues?view=sql-server-ver17#pbkdf2-hashing-algorithm-can-affect-login-performance

0 comments

Answer 2

After upgrading your SQL Server to version 2025, it's not uncommon to experience slower query performance. One potential cause could be related to changes in the Cardinality Estimation (CE) model that were introduced in SQL Server 2014 and continued in later versions. If your queries were optimized for an earlier version, they might not perform as well under the new CE model.

Here are some steps you can take to troubleshoot and potentially resolve the slow query performance:

Examine the query plan: Look at the execution plans for the slow-running queries to identify any inefficiencies.
Update Statistics: Ensure that the statistics for your tables are up to date, as outdated statistics can lead to poor query performance.
Identify Missing Indexes: Use the SQL Server Dynamic Management Views (DMVs) to find any missing indexes that could improve performance.
Rewrite Queries: Consider redesigning or rewriting the queries that are running slowly to optimize their performance.
Check Compatibility Level: Ensure that your database compatibility level is set appropriately for SQL Server 2025. Sometimes, reverting to a previous compatibility level can help improve performance until you can optimize the queries for the new version.

If all queries are running slower after the upgrade, the troubleshooting steps may differ, and you might need to investigate further into the specific causes of the performance degradation.

References:

Share via

Queries have been running really slowly since upgrading the database to SQL Server 2025.

1 additional answer

Your answer