"premature optimization is the root of all evil"

I would expect using a stored procedure would produce a measurable speed
difference primarily when it reduces the number of network or interprocess
calls, which is not likely to be the case with a simple
insert/update/delete.

IMO, if the use of stored procedures improves your design, use them,
otherwise measure the actual effect in a realistic environment.

david jencks

On 2002.12.21 10:48:07 -0500 The DeerBear wrote:
> Hello,
>
> As you had a chance to notice, I'm starting to create stored procs for my
> FB
> database.
>
> My idea was, in fact, to create a set of procedures to use( Insert,
> Select,
> etc ) for
> "basics" needs and use SQL directly only when _strictly_ necessary.
>
> To my understanding of the matter, in fact, stored procedures are
> executed
> on the
> server and only the results are returned to the client.
>
> So I was thinking that would maybe be faster if, for example, I used a
> stored
> procedure to make inserts into specific tables, instead of using direct
> SQL
> statements.
>
> Is this approach correct or you can point to other( better ) ways to make
> things faster with FB?
>
> TIA
>
> Andrew
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>