Hi there,
I think there are a few bad points:
1. Not as portable between databases as SQL
2. Harder to debug and test
3. A little harder to maintain [editing SQL in a CF page is easier than editing a stored procedure in a DB]
4. Need higher skilled developers to develop/maintain
5. Hard to develop with unless you have complete control over the DB [ie some shared hosting environments may have restrictions on their use]
6. May not give better performance
Not that I'm saying you shouldn't use them but only use them when they will give a benefit [usually performance].
In general I've found that CFCs + CF code can encapsulate the business logic better than using stored procedure but stored procedure can be used to improved performance [esp for repetitive tasks or large loops over data] where it is required.
From experience having to fix a badly written sorted procedure is a lot harder than trying to fix badly written cold fusion code ;-)
Justin
============================================= Justin Mclean Class Software Phone: (02) 93321230 9 Chapman St Fax: (02) 93321032 Surry Hills Mobile: 0416 119 342 NSW 2010 =============================================
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
