 | |
Duration incorrect on Profiler trace for SQL Server 2005
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Duration incorrect on Profiler trace for SQL Server 2005 -
06-05-2008
, 10:57 AM
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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 |
#4
| |||
| |||
|
|
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 |
#5
| |||
| |||
|
|
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 |
#6
| |||
| |||
|
|
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 |
#7
| |||
| |||
|
|
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 |
#8
| |||
| |||
|
|
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 |
#9
| |||
| |||
|
|
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 |
#10
| |||
| |||
|
|
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 |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.