One way in which stored procedures called using CFSTOREDPROC _could_ result
in a performance loss is that CF can't cache their results. I agree that
more complex queries are likely to benefit more; SPs have more fixed
overhead, which will make them worse than straight queries for simple
selects. As in everything else in programming, every query technique has
its place, and none is best at everything.
SPs potentially have other benefits, such as black-boxing (hiding the
details of your table structures, etc so you can change them later without
breaking existing programs) and security (in some DBMS' you can give users
rights to a SP without giving them rights to the underlying tables) which
could outweigh a performance penalty. Oftentimes hardware is cheaper than
labor...
-----Original Message-----
From: Robert Everland [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 27, 2000 10:39 AM
To: '[EMAIL PROTECTED]'
Subject: RE: do stored procedures REALLY help performance?
What I have found that if you do a stored procedure in a loop it defeats the
whole purpose of a stored procedure becuase you are doing the query over and
over again. Though just in theory it would work faster because instead of
cfquery building your query it would already be built for you. I figure it
would work better with inner and outer joins, the more complicated the query
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
