Thanks for the assistance, I will check the "Oracle SQL Developer Migration" .

yes that was 1204....because we have SQL server is 2000.

Please below find the errorlog trace out by DBCC

2009-01-11 21:52:12.57 spid4 -- next branch --,0

2009-01-11 21:52:12.57 spid4 ,0

2009-01-11 21:52:12.57 spid4 ...

Hi Grant,

Thanks....

IT's SQL Server 2000,

I will look into the deadlock issue ,that whether it is related to single session or not.

thanks,

But how deadlock manager kills the connection(transaction) . In my job deadlock is occuring within a loop in the Stored procedure,once deadlock occured ,transaction gets roolback, and we wants...

There is a sheduled job in my application......which runs on daily basis.but one in around two weeks it get failed. on the basis of the output file we found that...

Hi Gail,

Sorry for posting it in wrong location.

this is related to SQL server 2000.

i just open the dbcc trace.(“DBCC TRACEON (3605, 1204))

But while searching for the LOG directory in the C:\Program Files\Microsoft SQL Server\MSSQL(where the error logs gets save) i didn't got any LOG folder.

Since the server is production database server...

The DBCC TRACEON (1204,-1) statement is not showing the information about the deadlock.

but through DBCC TRACEON (3605,1204) we can trace the information related to the deadlock.

Hi Markus,

Thanks, Now i am able to trace out the deadlock through errorlogs.

Hi Markus,

I am very new to SQL profiler and i don't know whether i need to run the "DBCC TRACEON (1204)" statement in the SQL profiler in query analyzer or...