About every 3 months or so someone posts an error like this, hoping for an
easy solution....the answer is always a bit disappointing :)
In simple terms, deadlocks occur when two competing processes are holding
resources required by the other process to finish. As a result, neither
process would ever finish, and SQL Server randomly kills one of the
processes, allowing the other to finish.
Knowing this should help you to pinpoint possible "race" conditions within
your code, and take appropriate measures to limit possible deadlocks, and to
catch them whenever they do occur so the process can end gracefully.
> Hi there...
>
> i have a problem with some querys,dunno exactly whta query is cause
> cfcatch don't say anything about but this if i see the line points to
> <cftransaction> tag.
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 52)
> was deadlocked on {lock} resources with another process and has been
> chosen as the deadlock victim. Rerun the transaction.
>
>
> Any tips?
>
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201588
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
