Re: Profiler

From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 02/23/05 

Date: Wed, 23 Feb 2005 14:24:26 -0500

That is most likely coming from the Logout event. Remove that event from
the trace definition and it should go away. 

-- 
Andrew J. Kelly  SQL MVP
"anita" <anonymous@discussions.microsoft.com> wrote in message 
news:0d8c01c519dc$12c9c600$a601280a@phx.gbl...
> 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!
>