(my apologies if this gets posted twice, but the first one didn't seem to go through.)
My understanding and experience is that a well-architected application should NEVER experience a SQL deadlock. If I am incorrect in this premise, please let me know. Based on that assumption, I'm trying to diagnose a client's deadlock problem. They are a new client. I have a copy of their code and a copy of the error, but don't have access to their SQL Server 2005 database. I'm told the database has no stored procedures, no functions, triggers, or external jobs running on it, but I suppose that information is wrong. I'm getting this error: "Error","jrpp-717","06/09/10","13:47:16","SomeSiteName","Error Executing Database Query.[Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 187) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The specific sequence of files included or processed is: C:\Inetpub\wwwroot\SomeSiteName\index.cfm, line: 126 " There were three existing uses of <cftransaction> on the site, and I've temporarily set them all to "serializabile". I also had the client show me everywhere this particular table is written to (insert/update/delete) and have put a serializable cftransaction around that code. If this is the only code writing to this table, should I still be getting transaction deadlocks? Thanks, - Andrew. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:334430 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
