Quick Answer
Start with sys.dm_exec_query_stats sorted by total_worker_time or total_elapsed_time to find the costliest queries. Query Store gives historical data with plan regression tracking. Wait stats (sys.dm_os_wait_stats) show whether slowdowns are CPU, I/O, or lock-related. Always measure before tuning — don't guess.
Answer
To identify slow queries, examine:
sys.dm_exec_query_stats – CPU, I/O, execution time
sys.dm_exec_requests – currently running queries
sys.dm_tran_locks – blocking analysis
Extended Events – deep tracing
Query Store – historical regressions
This helps pinpoint which query and which operator is causing server slowdown.
S
SugharaIQ Editorial Team
Verified Answer
This answer has been peer-reviewed by industry experts holding senior engineering roles to ensure technical accuracy and relevance for modern interview standards.
