HostWeb Forums » Microsoft Databases » microsoft.public.sqlserver.tools » Duration incorrect on Profiler trace for SQL Server 2005

Topic: Duration incorrect on Profiler trace for SQL Server 2005

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 6/5/2008 9:57:01 AM

By: Anonymous
I'm aware that profiler can show duration in microseconds. I'm running a
trace for a specific DB where the duration is incorrect. If I manually
subtract starttime from endtime, I'm seeing what I'm sure are accurate times
(generally about 1/2 second). For these statements that take 1/2 second
realtime, duration is displayed in the neighborhood of 54,###,###, (and
sometimes it shows massive negative numbers). That would be 54 seconds in
microseconds, or 54,000 seconds in milliseconds - I'm 100% sure neither is
correct.
Under Tools, Options "show in microseconds" is unchecked. If I check it, it
just adds 3 digits, as expected, but still is incorrect.

Has anyone else seen this behavior and is there a workaround that doesn't
involve writing to a SQL table and running SQL to get duration?

Thanks.
--
Kevin

Replies below ↓

Replies

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 6/7/2008 9:33:00 PM

By: Anonymous

RE: Duration incorrect on Profiler trace for SQL Server 2005

I wonder if this has anything to do with processor time drift. See
http://support.microsoft.com/kb/931279

Linchi

"KevinL" wrote:

> I'm aware that profiler can show duration in microseconds. I'm running a
> trace for a specific DB where the duration is incorrect. If I manually
> subtract starttime from endtime, I'm seeing what I'm sure are accurate times
> (generally about 1/2 second). For these statements that take 1/2 second
> realtime, duration is displayed in the neighborhood of 54,###,###, (and
> sometimes it shows massive negative numbers). That would be 54 seconds in
> microseconds, or 54,000 seconds in milliseconds - I'm 100% sure neither is
> correct.
> Under Tools, Options "show in microseconds" is unchecked. If I check it, it
> just adds 3 digits, as expected, but still is incorrect.
>
> Has anyone else seen this behavior and is there a workaround that doesn't
> involve writing to a SQL table and running SQL to get duration?
>
> Thanks.
> --
> Kevin

Contents
Home
Forums
About Us
Contact Us
Web Hosting:
Hosting Providers
How to choose a name
What is a Hosting Provider
Hosting Types
Choosing the right plan
 
Search
 
Login to HostWeb.com
Email
Password
If you do not have an account with us yet, join now - it's FREE!