You Only Have Two Choices To Improve SQL Server Performance

So often I get asked how to improve performance within SQL Server. I make a set of suggestions only to be told that no changes can be introduced. Well, without changes, you can't improve performance. In this video I review exactly what you need to do in order to improve performance within SQL Server. There are only two choices and you have to pick one.
#sqlserver #performancetuning #querytuning

[nilsfrahm]

I can give you ideas: Use query store, capture query plans, find one that used to run faster and force that one.
Check if problem was caused by parameter sniffing, if you can alter code a bit, add option(recompile) or option(optimize for unknown).
Check if some queries can use snapsot isolation (i.e. consistency not absolute critical) and enable that and use for some, it decreases locking.
Check if using table functions, avoid them, check if deadlocks are mentioning them.
Check if triggers cause deadlocks.
Check if plans are bad due to Nested loops (cardinality issue), for some tables you can force Hash join with hints.
Check db compatibility level, try using latest, like 2019 option.
Use profiler, check query captured but also SET options, like arithabort or isolation level.
There are things to check...

[DanielMaenle]

Thank you for the video, I enjoy each video you let out.

[NeverForget]

So out of curiosity what other ways do some think you can fix performance issues if it's not better hardware or code changes?