Strange durations in Profiler

#31

May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.

I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)

Anand

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

I wonder if this has anything to do with the cpu time drift. Do you see
any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?

Linchi

"jim.steiner (AT) rackspace (DOT) com" wrote:

When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?

#32

May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.

I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)

Anand

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

I wonder if this has anything to do with the cpu time drift. Do you see
any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?

Linchi

"jim.steiner (AT) rackspace (DOT) com" wrote:

When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?

#33

May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.

I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)

Anand

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

I wonder if this has anything to do with the cpu time drift. Do you see
any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?

Linchi

"jim.steiner (AT) rackspace (DOT) com" wrote:

When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?

#34

May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.

I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)

Anand

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

I wonder if this has anything to do with the cpu time drift. Do you see
any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?

Linchi

"jim.steiner (AT) rackspace (DOT) com" wrote:

When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?

#35

May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.

I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)

Anand

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

I wonder if this has anything to do with the cpu time drift. Do you see
any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?

Linchi

"jim.steiner (AT) rackspace (DOT) com" wrote:

When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?

#36

May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.

I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)

Anand

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

I wonder if this has anything to do with the cpu time drift. Do you see
any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?

Linchi

"jim.steiner (AT) rackspace (DOT) com" wrote:

When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?

#37

May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.

I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)

Anand

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

I wonder if this has anything to do with the cpu time drift. Do you see
any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?

Linchi

"jim.steiner (AT) rackspace (DOT) com" wrote:

When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Strange durations in Profiler

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools

Re: Strange durations in Profiler - 07-30-2008 , 09:32 AM

Re: Strange durations in Profiler - 07-30-2008 , 09:32 AM

Re: Strange durations in Profiler - 07-30-2008 , 09:32 AM

Re: Strange durations in Profiler - 07-30-2008 , 09:32 AM

Re: Strange durations in Profiler - 07-30-2008 , 09:32 AM

Re: Strange durations in Profiler - 07-30-2008 , 09:32 AM

Re: Strange durations in Profiler - 07-30-2008 , 09:32 AM