Profiler

From: anita (anonymous_at_discussions.microsoft.com)
Date: 02/23/05 

Date: Wed, 23 Feb 2005 11:15:44 -0800

Running profiler to catch anything on the server that has
a duration of greater than 30,000 miliseconds(30 sec),
and realisticly we shouldn't have much logged, but in 3
hours we have over 23,000 rows logged and most of the
rows text data is recording this:
-- network protocol: TCP/IP
set quoted_identifier on
set implicit_transactions off
set cursor_close_on_commit off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set language us_english
set dateformat mdy
set datefirst 7

What does this mean? And why is this running so long?
Thanks!

Relevant Pages

  • Re: SQL Service saturating CPU
    ... The Service uses an average of 99% of CPU time, ... Try running profiler for a while and see what is going on in the system. ... the current activity command. ... Turn on Performance Monitor and track the CPU usage for SQL Server for a few ...
    (microsoft.public.sqlserver.server)
  • track high compilationssec
    ... Also the recompilations\sec are averaging at 0 which seems to be ... looked at Profiler but i see a recompile event. ... Besides Ive got around 2000 batch requests\sec on this server and ... running profiler would bring it to its knees. ...
    (microsoft.public.sqlserver.server)