Re: when to use stored procedures

Mark Lybarger wrote <4fHi4.1943$K5.16840_at_newsfeed.slurp.net>...
>The question is, from a design prospective, when is
>it best to use stored procedures? What are the advantages/disadvantages.

stored procedures are useful
- whenever you want to have functions done in a similar way throughout an application (modularization)

- whenever you want to have the chance to change code 'dynamically'
- whenever you want to provide basic code functionality to every team member
- you name it ...

e.g. we developed a software contolling an automatic conveyor system, and the strategies for allocating storage spots have not been very clear at the beginning of the development - so we did everything in stored procedures - defined the interfaces and changed the code dynamically according to the growth of knowledge - no recompiling of (C-coded) demons, easy testing with SQL, ... another project: common tasks to be done like inventory control - or - logging - functional primitives coded once with well-defined interfaces - here you go -

generally speaking - whenever you want / need a peace of similar funtionality in more than one place in your application software, stored procedures could be of help

regards Received on Mon Jan 24 2000 - 21:26:00 CST