But point worth noting, if you are using SQL Server you could actually be
using SP's without knowing it. There is a driver option (often on by
default) in the SQL Server Control Panel applet that instructs Sql Server to
auto-generate a SP for submitted SQL statements. These persist for the
active connection, so you could be reusing SP's and getting some of the
benefit of doing so already.
--- Ben
-----Original Message-----
From: Michael Smith [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 3:37 PM
To: CF-Community
Subject: Re: Stored procedures...when would you
Great discussion on SPs and Views! I would add another reason not to do
SPs - they are harder to debug from CF that
straight SQL - when it doesn't work you don't get a good error message from
CF... Of course the regular CFQUERY
error message isn't great either but at least you can cut and paste the SQL
back into your query builder to test...
I think writing SPs takes longer than inline SQL - with two enviroments (CF
and SQL ent manager) and testing. Only
makes sense on speed or load critical code. Straight SQL is better for
prototyping too for this reason.
- Michael Smith, TeraTech, Inc http://www.teratech.com/
Angel Stewart wrote:
> NOT want to use stored procedures to run queries etc. on a database?
>
> Wouldn't a stored procedure almost always run faster than one done through
> CF?
>
> -Gel
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
