How to analyze SQLProfiler trace result ?

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
[url]http://groups.google.co.id/group/microsoft.public.sqlserver.programming/browse_thr
ead/thread/fc287e2b9eb78b92/a05b0496982d258b?lnk=st&q=&rnum=24#a05b0496982d258b[/u
rl])
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,
xtantoA timeout is called "Attention" in Profiler. So make sure you catch that eve
nt. 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/
<krislioe@.gmail.com> wrote in message news:1155353854.603424.64300@.74g2000cwt.googlegroups.c
om...
> 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
> [url]http://groups.google.co.id/group/microsoft.public.sqlserver.programming/browse_t
hread/thread/fc287e2b9eb78b92/a05b0496982d258b?lnk=st&q=&rnum=24#a05b0496982d258b[
/url])
> 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
>