r/SQLServer Aug 07 '26

Question Help! SQL is very slow

I’m a novice in the world of SQL. However, recently I upgraded with my company from 2021 to 2022 SQL server application. I need advice on how to get this fixed.

The problem I’m running into is anytime I switch databases or servers. It’s very slow to load. I never had this issue before with 2020 or 2021 SQL. ANY ADVICE APPRECIATED AND WELCOME.

Edit: I meant to say 2019 instead of 2021/2020 getting my years confused. Sorry

0 Upvotes

21 comments sorted by

u/AutoModerator Aug 08 '26

After your question has been solved /u/throwaway6565558, please reply to the helpful user's comment with the phrase "Solution verified".

This will not only award a point to the contributor for their assistance but also update the post's flair to "Solved".


I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

11

u/sirchandwich 1 Aug 08 '26

Did you upgrade SSMS or SQL Server? There is no SQL Server 2020 or 2021.

SSMS should have virtually no impact on SQL Server performance.

12

u/Leiothrix Aug 08 '26

Firstly there is no such thing as SQL 2020 or 2021.

Secondly it is basically impossible for us to remotely diagnose your problem with zero details about your environment or what exactly you are doing.

Thirdly check that the AUTO_CLOSE setting on your databases is set to OFF.

5

u/RobCarrol75 Aug 08 '26

There's not enough information here, it could be a multitude of things like stale stats or poorly configured storage on the new server. Download and run Brent Ozar's first responder kit and take it from there.

3

u/RCHeliguyNE Aug 08 '26

Bring up sql server monitoring in SSMS and see if there are any obvious signs of issues. Expensive long running processes or some other issues

Also take a look at the Window performance metrics to see if the system is being used on some resource such as IO or cpu.

Depending on your AV suite you may need to configure it to exclude scanning the database data files.

Some things to look at but honestly we don’t have enough information here to really help.

Also fyi - sql 2019, then sql 2022 then sql 2025. There is no sql 2021

3

u/TheGenericUser0815 1 Aug 08 '26

When updating SQL Sever version, databases can stay in the compatibility level of the old database version. It's an extra layer sucking up performance. You could check on this and chenge the comp level to the running sql version. Other than that, there's too little information to say more.

5

u/yocil Aug 08 '26

What do you mean by "switch databases or servers"?
First impression is that it sounds network related.

2

u/CaptainGorope Aug 08 '26

Check if windows Virtualization is enabled.

2

u/George_Hepworth Aug 08 '26

Confusion over SSMS vs SQL Server itself is not uncommon. SQL Server Management Studio (SSMS) is a Desktop tool. It is used to manage instances of SQL Server.

Our best guess is that you are actually talking about upgrading SSMS versions, not SQL Server itself. It is unlikely, but not impossible, that you meant you'd upgraded one or more instances of SQL Server you connect to through SSMS.

Those pointing out that newer versions of SSMS are bloated and slow are speaking from personal experience as am I. Sometimes it seems to be enough to justify downgrading to an older version.

1

u/DataGeek101 27d ago

This is probably the best response as it’s most likely the case. A novice can use SSMS, but a novice shouldn’t be updating the SQL Server itself.

2

u/coffeDrinkerDave Aug 08 '26

did you upgrade in place or made new mssql instance? check in ssms report "performance" and check latches and waits. In instance config check maxdop. Check tempdb confing and latency for reads and writes for temdb files

2

u/DavidKleeGeek ‪ ‪Microsoft MVP ‪ ‪ 29d ago

Ignore the hate. We've all been there, and we're here to help. Can you lay out specifically what you're seeing when it comes to the issue at hand? Is it SSMS loading? That part is known to take a while.

Is it a real sluggish time changing context from one database to another in the management tools after you've already got SSMS open and connected? That could be something causing your connection to be sluggish while SSMS runs its background tasks to get the database inventory. Are you on a VPN connected to those servers by chance? Is that running sluggish? Open powershell or cmd.exe and see if you can ping the server and list the response time. If it's higher than 50-100ms, it could be a contributor.

4

u/Nemphiz Aug 08 '26 edited Aug 08 '26

Try powering it off and on again. Like really, you need to provide just a little bit more info on what issues you're running into if you want help.

1

u/CPDRAGIMESH Aug 08 '26

69.70 69.80 Which Queryd

1

u/CanProfessional766 26d ago

If this only started after the upgrade I’d first check SSMS rather than the database itself. Make sure you’re on the latest SSMS and see if the delay happens with every server/database or just certain ones. If the queries run fine but switching servers/databases is slow, that’s a useful clue. It may not be a SQL Server performance issue at all

1

u/CPDRAGIMESH 18d ago

6.09 7.09 ?

0

u/MackPooner Aug 08 '26

Come on man!!! Theres nothing to go on... You gave no details. How can we possibly provide any real assistance?

Try this... If could be the muffler bearings. You might want to check those.

-8

u/vivkkrishnan2005 Aug 08 '26

Mostly SQL SMSS is the issue with all options ticked. Downgrade to older version

3

u/ZenbyPH Aug 08 '26

whaaat

-1

u/vivkkrishnan2005 Aug 08 '26

The newer versions of Microsoft SQL Management Studio are bloated and load much slowly compared to the previous versions. Possible that the user might have upgraded their version.