How to analyze SQLProfiler trace result ?

12 Aug 2006 3:37 AM

krislioe

Hi All,

I plan to run SQL Profiler because my SQL Server 2000 get the users
timed out after running some time, and happen every day.
(see
http://groups.google.co.id/group/microsoft.public.sqlserver.programming/browse_thread/thread/fc287e2b9eb78b92/a05b0496982d258b?lnk=st&q=&rnum=24#a05b0496982d258b)

The question is :
After I get the trace recorded using Profiler, how can I check which
query that cause the problem ?
Or what I see any clue of the problem on the SQL Profiler result ?

Thank you very much,
xtanto

12 Aug 2006 7:24 AM

Tibor Karaszi

A timeout is called "Attention" in Profiler. So make sure you catch that event. You can now go
backward for a SPID, from the Attention to the SQL:BatchStarted (or similar) event to see what query
was timed out.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/

Show quote

<krisl***@gmail.com> wrote in message news:1155353854.603424.64300@74g2000cwt.googlegroups.com...
> Hi All,
>
> I plan to run SQL Profiler because my SQL Server 2000 get the users
> timed out after running some time, and happen every day.
> (see
> http://groups.google.co.id/group/microsoft.public.sqlserver.programming/browse_thread/thread/fc287e2b9eb78b92/a05b0496982d258b?lnk=st&q=&rnum=24#a05b0496982d258b)
>
> The question is :
> After I get the trace recorded using Profiler, how can I check which
> query that cause the problem ?
> Or what I see any clue of the problem on the SQL Profiler result ?
>
> Thank you very much,
> xtanto
>

13 Aug 2006 4:48 AM

xtanto

Hi Tibor,
Thanks for your answer.

Actually what I want to find with Profiler is not the query that was
timed out, because when the "specific condition" met, "any queries" to
the server, from "any user" will get timed out.

So my goal is to find What Has caused this "specific condition" ?

Thank you very much,
xtanto

Tibor Karaszi menuliskan:
Show quote

> A timeout is called "Attention" in Profiler. So make sure you catch that event. You can now go
> backward for a SPID, from the Attention to the SQL:BatchStarted (or similar) event to see what query
> was timed out.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> <krisl***@gmail.com> wrote in message news:1155353854.603424.64300@74g2000cwt.googlegroups.com...
> > Hi All,
> >
> > I plan to run SQL Profiler because my SQL Server 2000 get the users
> > timed out after running some time, and happen every day.
> > (see
> > http://groups.google.co.id/group/microsoft.public.sqlserver.programming/browse_thread/thread/fc287e2b9eb78b92/a05b0496982d258b?lnk=st&q=&rnum=24#a05b0496982d258b)
> >
> > The question is :
> > After I get the trace recorded using Profiler, how can I check which
> > query that cause the problem ?
> > Or what I see any clue of the problem on the SQL Profiler result ?
> >
> > Thank you very much,
> > xtanto
> >