Deadlock, Rerun the transaction

I always get the following error, when someone is trying
to to access our live site, the database recoirds are
more, how to get away with this problem.
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction
(Process ID 53) was deadlocked on {lock | communication
buffer} resources with another process and has been chosen
as the deadlock victim. Rerun the transaction.Hi Bharathi,
This might be useful for you to solve the issue.
http://www.sql-server-performance.com/deadlocks.asp
Sankar Renganathan
DBA, SPAR Group Inc.,
Please reply only to the newsgroups.
This posting is provided AS IS with no warranties, and confers no rights.
"Bharathi" <vamsi5@.hotmail.com> wrote in message
news:022201c3d6fa$6ba96ee0$a601280a@.phx.gbl...

quote:

---

> I always get the following error, when someone is trying
> to to access our live site, the database recoirds are
> more, how to get away with this problem.
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction
> (Process ID 53) was deadlocked on {lock | communication
> buffer} resources with another process and has been chosen
> as the deadlock victim. Rerun the transaction.
>

---

|||very fuzzy! I got a similar error o a DTS that export a table in a .XLS: ...
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
Error string: Transaction (Process ID 55) was deadlocked on lock resou
rces with another process a
nd has been chosen as the deadlock victim. Rerun the transaction. Error
source: Microsoft OLE DB Provider for SQL Server Help file: He
lp context: 0 Error Detail Records: Error: -2147467259 (80004005
); Provider Error: 1205 (4
B5) Error string: Transaction (Process ID 55) was deadlocked on lock r
esources with another process and has been chosen as the deadlo... Process
Exit Code 1. The step failed.
I got the error both on scheduled JOB (by night) that run the DTS and starti
ng the job NOW...
So I run a trace with SQL Profiler and it works... ;-) It is not the first t
ime that tracing a process to find an error... the process doesn't fail
So...: "Fear it! And it will works!"
Ciao
Leonardo
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...