0

As seen in this screen shot, I'm running the same query over and over again, comes back with 0 rows (as expected). For some reason I'm seeing very large wait times on server replies while running this on the server itself. I was wondering if someone could point me in the right direction as to why this might be occurring.

My guess is that its lack of resources or too many other things occurring but wondering how I can prove that.

MSSql server 2017 standard edition 64 core machine, 240 GB of ram

EDIT: output of wait stat added. 42 rows.

enter image description here

enter image description here

3

1 Answer 1

1

The comments on the main post above was super helpful. It lead me to find that I was getting millions of CMEMTHREAD waits and that this was in fact not normal.

select distinct wait_type, sum(waiting_tasks_count), avg(wait_time_ms) 
from  sys.dm_exec_session_wait_stats
group by wait_type
order by 2 desc

The above showed me the huge wait times on the temp table for resources, this lead me to an article mentioning that this issue is fixed in Cumulative Update 16 in SQL server 2017.

I ran select @@version and saw that I was running a RTM-GDR version of 2017 (unlike my other servers) and that only takes high priority security updates, not CU changes which I seem to need.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.