<forgive me if you have tried this already...this approach has worked well for me in past>
Do you have access to the SQL Server Query Analyzer? If so, you can use the Estimated Execution plan button to see how the query optimizer is going to execute your query. This is where you can determine if your query is actually using the index you want it to or not. If there is an index on the table that you think the query should be using but it's not indicated as being used, try reworking the query so that the indexed columns appear first in the query statment. If there is not an index on the table, you should probably create one that corresponds to the most frequently used ones HTH, Mike Mike Flanigan UPSHOT Marketing Director of E-Solutions Office 804.422.9673 Cell 804.357.1259 http://www.upshot.net/ -----Original Message----- From: Jon Hall [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 3:19 PM To: CF-Community Subject: Re: OT: MS SQL Server What does the CPU load look like? If it's high then you have to look at reducing some of the locks. Check out this program http://www.sqlservercentral.com/products/sqlspy/ It's a nice way to watch database activity, and see exactly what is causing problems realtime. Not closing any recordsets or using the wrong kind of recordsets, or if you are using recordsets to do anything other than immediately stick the the results in an array (if it's a select statement), on a highly trafficed site all those would definately cause deadlock problems... jon ----- Original Message ----- From: "Shawn Regan" <[EMAIL PROTECTED]> To: "CF-Community" <[EMAIL PROTECTED]> Sent: Thursday, March 14, 2002 2:59 PM Subject: RE: OT: MS SQL Server > No I am not using transactions. This is with an ASP site but we are getting > deadlocks with the database. > > -Shawn Regan > > -----Original Message----- > From: Nick McClure [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 14, 2002 11:27 AM > To: CF-Community > Subject: Re: OT: MS SQL Server > > > You are using transactions? When two (or more) transaction collide, one of > the will get deadlocked, it will throw an error and the transaction is > rolled back. > > You have to be very careful when using transactions, if things are being > accessed by multiple people and a lot of things are going on, this can > happen. > > At 10:32 AM 3/14/2002 -0800, you wrote: > >What is happening when cold fusion or asp is returning a "SQL Dead lock" > > > >-Shawn Regan > > > > > > ______________________________________________________________________ Macromedia ColdFusion 5 Training from the Source Step by Step ColdFusion http://www.amazon.com/exec/obidos/ASIN/0201758474/houseoffusion Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
