Re: pros and cons of using stored procedures

Can't recommend any books, etc. but I can think of a couple of points to make:

(1) I typically try to separate application behavior from

    data behavior. Any behavior that is a characteristic of     the data I implement using stored procedures. This way,     the data and its behavior are encapsulated in the database     and the behavior doesn't need to be duplicated across all     of the applications that sit on top of the database (with     the risk its duplicated inconsistently).

(2) Stored procedures can be used as a means to push certain

    processing onto the database server although this is DBMS     specific. I know Oracle and Informix both execute stored     procedures on the server. I supposed a DBMS (eg. ObjectStore)     that does client-side processing and caches a lot of data     on the client might execute stored procedures on the client.

Hope this helps.

Roger Tomas
AG Communication Systems

Rusty Wright wrote:
>
> Can anyone recommend a book, web page, etc. that explains the pros and
> cons of using stored procedures, as opposed to putting the code in
> your front-end code? The background info is that a group of us are
> designing a database and we'll be using Oracle, and for the front-end
> we'll be using a web interface probably with the PHP scripting
> language as the glue.
>
> One of the people on the team is a proponent of using stored
> procedures and another is against it. Obviously, none of us are
> database experts and I'd like to be able to read up on stored
> procedures so that we can argue the issue intelligently.
>
> Thanks
Received on Wed Sep 12 2001 - 20:07:56 CEST