Subject | Re: Stored procedures vs Dynamic SQl |
---|---|
Author | women_lover_best |
Post date | 2005-07-14T05:47:20Z |
Hi Helen,
thanks for replying..
My situation..
does firebird saves execution plan both for Sp and dynamic SQL's..is
there a performance difference?
What I meant was.. SQL server 2000...saves execution plan of stored
procedures as well as Dynamic SQL.. what does Firebird do? We r
developing an application which uses client(smart in .net) and
server in .net, and Firebird as database.I would like to go for
Dynamic SQL(using LLBgen like product)..as I feel maintaning stored
procedures is a painful job..
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
thanks for replying..
My situation..
does firebird saves execution plan both for Sp and dynamic SQL's..is
there a performance difference?
What I meant was.. SQL server 2000...saves execution plan of stored
procedures as well as Dynamic SQL.. what does Firebird do? We r
developing an application which uses client(smart in .net) and
server in .net, and Firebird as database.I would like to go for
Dynamic SQL(using LLBgen like product)..as I feel maintaning stored
procedures is a painful job..
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
> At 07:40 PM 13/07/2005 +0530, you wrote:SP or
> >Hi,
> >
> >I would like to know if there is a huge difference between using
> >Dynamic SQL.I am in process of deciding an architecture whereclients
> >will be .net smart client,and firebird1.5..I have about 120-130central
> >tables..Clients,will be of POS terminal type..connected to a
> >server..making an
>
> Yes, like there's a huge difference between peeling an apple and
> apple pie. They are different eating experiences. If you have anoperation
> that is achieved by a simple insert, update or delete statement,it doesn't
> make sense to push that work into a stored procedure. If you havea
> complex operation that imvolves updating multiple tables or (inthe case of
> selects) needs a set that couldn't be got easily with a singleDSQL
> statement, then you want a stored procedure.the pie.
>
> If you only want to eat the apple, don't make the pastry and bake
>
> ./heLen