May 15, 2014 at 3:58 am
Hi Team,
Executing a query in SSMS, it is taking "1 min 24 seconds", while monitoring the same in sql profiler duration is showing as '80506' milliseconds, i.e '1 min 34 seconds'
There is difference in 10 seconds, can you please explan why..
May 15, 2014 at 4:46 am
Sure, the duration in SSMS includes the time it takes to move the query and the results across the network. Trace and extended events just measure the time it takes the query to execute on the server.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 15, 2014 at 5:01 am
Minnu (5/15/2014)
while monitoring the same in sql profiler duration is showing as '80506' milliseconds, i.e '1 min 34 seconds'
80506 ms is not 1 min 34 sec.
It's 80.5 seconds. 60 seconds in a minute, so that profiler duration is 1 minute 20.5 seconds. Less than what SSMS shows, because SSMS's duration includes the time of displaying the data which SQL Server doesn't.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply