June 7, 2013 at 5:43 am
Hi
I have a sp which is timing out on my website. When i run a trace on it, duration comes ~ 80000 (ms)
So it times out as it is set 30s for site. but when I run the same call after copying from trace in SSMS, it hardly takes 2-3 secs. Why profiler show long durations?
I tries same thing for 5-10 calls to be sure that it is not because of cached data. but they are always fast on SSMS.
Is duration column in profiler accounts for Network time or any other times in it?
Online Trainer For SQL DBA and Developer @RedBushTechnologies with 18 yrs exp.
June 7, 2013 at 7:10 am
The version that you are running may well have a different query plan. You may have an issue with parameter sniffing.
SQL DBA
Every day is a school day, and don't trust anyone who tells you any different.
http://sqlblogness.blogspot.co.uk
June 8, 2013 at 3:17 pm
You could also be experiencing blocking. Run one proc now and a statement within it might be blocked for some reason and the proc could take 30 seconds. Run that same proc 60 seconds later and it might complete with no issues in 2-3 seconds.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply