If I remember correctly, the trace event 1024 occurs when a deadlock between
two process has happened and has been broken by SQL-Server. You could set a
TraceOff on the event 1024; however, a better idea would to correct the
situation at its source and change the code responsible for the occurence of
these deadlocks (but it won't be an easy task).
You should search the BOL for « Troubleshooting Deadlocks » and ask your
question in a more specific newsgroup such as m.p.sqlserver.programming .
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
"Kyssling" <kyssling[ at ]email.cz> wrote in message
news:uJBor5nmGHA.3296[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Goof morning,
>
> I still have in the event log next messages :
>
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 28.6.2006
> Time: 8:21:44
> User: N/A
> Computer: XY
> Description:
> 17550 :
> DBCC TRACEON 1204, server process ID (SPID) 56.
>
> Maybe it is possible colision in our SQL application, or anybody write me
> some next informations.
>
> Very thanks Kyssling
>
>
|