0

We are on SQL Server 2017

Application was set to run PROC up to 5min. So if it exceed 5mins it is going to timed out.

The PROC got timedout, when I see the history of that query in sp_whoisactive which we store history in our log table): the reads, writes are 0. There are no waits and no blockings. The status in in RUNNABLE. CPU shows 0 in sp_whoisactive. Couldn't find the reason why it ran 5min. Normally this PROC executes in 20 seconds

Any inputs ?

I tried by checking if there any blockings or waits which I see none. Since the query is in runnable state I expect it to consume CPU OR having any reads or writes which I find 0. Couldn't find a way to know what exactly happened.

I tried to reproduce the issue but it ran successfully. Need help in finding the root cause and not to see outage again.

Please help

0 Answers0