Take the app down? Increment? I am not sure what server you were on but none of that is necessary.
"This e-mail is from Reed Exhibitions (Oriel House, 26 The Quadrant, Richmond, Surrey, TW9 1DL, United Kingdom), a division of Reed Business, Registered in England, Number 678540. It contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender or call our switchboard on +44 (0) 20 89107910. The opinions expressed within this communication are not necessarily those expressed by Reed Exhibitions." Visit our website at http://www.reedexpo.com -----Original Message----- From: Zaphod Beeblebrox To: CF-Talk Sent: Sun Aug 27 23:29:16 2006 Subject: Re: Stored procs (was Top 100 ColdFusion Programmers) I did a project where sp's were used almost exclusively. That was a major pia whenever it came to moving the app from dev to production. Usually, you can role an update to production by just copying over the cfml. Changes in sp's required you to either increment the sp name, or take the app down while you rolled out the sp change. Either way, it was a pia. On 8/27/06, Snake <[EMAIL PROTECTED]> wrote: > While on that subject, a lot of people insist that everythig should be done > with SP's wherever possible. > While this is indeed a good idea for long/complex queries that will see > vastly improved performance and speed, but I think it is wrong to do it just > for the sake of it, and to put basic select or other small queries etc into > SP's. > One of the primary reasons being that where contractors are involved, they > will often have access to the CFML only and not the database server, and > thus cannot access the stored proc, which can seriously slow down > development time while they wait for the DBA to send them a copy of the SP, > and then change it, send it back to the DBA, wait for him to apply it etc. > Also it is in general a pain if you need to do quick fixes or updates on > code in general. Usually it is easy to gain access to the code via FTP from > wherever you are as this is generally an open port, but not to the DB > server, as you will either need remote access to port 1433 or remote desktop > access. neither of which may be obtained quickly or easily as they > should/would be blocked from the outside world via a firewall. > > Just my 2p > > Snake > > -----Original Message----- > From: Robertson-Ravo, Neil (RX) > [mailto:[EMAIL PROTECTED] > Sent: 27 August 2006 13:42 > To: CF-Talk > Subject: Re: Top 100 ColdFusion Programmers > > Again, and the point has been echoed by James, is that the all-rounder > should know both. > > I am not saying that SPs etc (not that has anything to do with you level of > SQL per se) are what you should know, we all know that ColdFusion can do a > lot with loops and SQL but if you have no choice but to use SQL in a job, > you will be stuffed if all you know SELECT. > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:251195 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
