:-) well from a database point of view you are wanting to do one of two things.....[a] stop the offending process happening BEFORE it gets to the SQL Server or [b] allow the process to commit but to be setup in the queue on the SQL side....
both as equally as sound, but obviously CF is easier from a variety of angles. My guess would be to put in cflocks around the insert queries which, would obviously stop any deadlock on the CF and then in turn the SQL side. You could the obivously do cftransaction as well, but I cant see where that would help in this situation as all you want to do its "queue" requests up. -----Original Message----- From: Rich Wild [mailto:[EMAIL PROTECTED] Sent: 17 October 2003 15:25 To: '[EMAIL PROTECTED]' Subject: RE: [ cf-dev ] sql deadlocks I'm not sure how you're helping. I have 2 pages - one to add a post to a thread and another to select the entire thread and display it. the two aren't connected. A transaction won't help. The problem occurs when users are attempting to add posts at exactly the same time. They may be on the same thread, they may not, its irrelevant. How can I adjust the queries from within CF to avoid this happening? Ah, Its Friday. I'm tired. > -----Original Message----- > From: Robertson-Ravo, Neil (RX) > [mailto:[EMAIL PROTECTED] > Sent: 17 October 2003 15:13 > To: '[EMAIL PROTECTED]' > Subject: RE: [ cf-dev ] sql deadlocks > > > Well, straight off, you should really be running > transactions, even if its cftransaction as that will help the > deadlocking problem straightaway. > > To trace, you need to use SQL Profiler....Start Programs > > SQL Server > SQL > Profiler. Select New > Trace and set up you SQL Server. > From within this > tool you can run a trace on literally just about ANYTHING. > > Let me know if you need any more info as servers are > different and need different profile traces. > > N > > > -----Original Message----- > From: Rich Wild [mailto:[EMAIL PROTECTED] > Sent: 17 October 2003 15:13 > To: '[EMAIL PROTECTED]' > Subject: RE: [ cf-dev ] sql deadlocks > > > I'm not running transactions no. > > I'm doing straight inserts and selects from CF. > > > necessary info to trace the lock. You also ay want to run > > an update lock > > rather than an exclusive lock (as Access does)...that way SQL > > Server will manage the locking internally on a better scale. > > How do I do this? > > > -----Original Message----- > > From: Robertson-Ravo, Neil (RX) > > [mailto:[EMAIL PROTECTED] > > Sent: 17 October 2003 15:06 > > To: '[EMAIL PROTECTED]' > > Subject: RE: [ cf-dev ] sql deadlocks > > > > > > Hey Rich, > > > > This just sounds like a simple case of trying to get the info > > on the deadlock. Are you running any transactions on the > > queries you have? If you need to, run the SQL Trace tool > > with a flag of 1205, this will give you the > > necessary info to trace the lock. You also ay want to run > > an update lock > > rather than an exclusive lock (as Access does)...that way SQL > > Server will manage the locking internally on a better scale. > > > > Let me know if you need any more info/sp's on locking and debugging. > > > > Neil > > > > > > > > > > -----Original Message----- > > From: Rich Wild [mailto:[EMAIL PROTECTED] > > Sent: 17 October 2003 14:23 > > To: '[EMAIL PROTECTED]' > > Subject: [ cf-dev ] sql deadlocks > > > > > > Hmm, having some trouble with some forums I've got that are > > getting busy. > > > > Occasionally I'll get deadlock error messages back from odbc > > about the fact that the process I'm using was chosen as the > > victim of a deadlock. > > > > How can I avoid these? > > > > The site is on a fairly cheap shared setup, so can't change > > the hardware etc.. > > > > ------------------------------------------------------- > > Rich Wild > > Senior Web Developer > > > > ------------------------------------------------------- > > e-mango Tel: 01202 755 300 > > Gild House Fax: 01202 755 301 > > 74 Norwich Avenue West > > Bournemouth Mailto:[EMAIL PROTECTED] > > BH2 6AW, UK http://www.e-mango.com > > ------------------------------------------------------- > > This message may contain information which is legally > > privileged and/or confidential. If you are not the intended > > recipient, you are hereby notified that any unauthorised > > disclosure, copying, distribution or use of this information > > is strictly prohibited. Such notification notwithstanding, > > any comments, opinions, information or conclusions expressed > > in this message are those of the originator, not of > > e-mango.com ltd, unless otherwise explicitly and > > independently indicated by an authorised representative of > > e-mango.com ltd. > > ------------------------------------------------------- > > > > > > -- > > ** Archive: > http://www.mail-archive.com/dev%> 40lists.cfdeveloper.co.uk/ > > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] For human help, e-mail: > > [EMAIL PROTECTED] > > > > -- > > ** Archive: > http://www.mail-archive.com/dev%> 40lists.cfdeveloper.co.uk/ > > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] For human help, e-mail: > > [EMAIL PROTECTED] > > > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
