Re: "Business Logic / Rules should never be in the database or stored procedures"

From: Tim X <>
Date: Mon, 14 Dec 2009 17:58:52 +1100
Message-ID: <>

"Gerard H. Pille" <> writes:

> BChase wrote:
> ...
>> What is my problem ? Well assuming I am not misinterpeting things, my Enterprise Architect area and some non-Oracle knowledge
>> architects feel that the business logic / rules should only be in the application tier.
> Business logic in the database has faster access to the data, so if a lot of
> data is needed ... In the application layer it is closer to the user, so when
> you want to be user friendly ...
>> Only Create, Read, Update, and Delete operations belong in stored procedures.
> A number of expressions spring to mind that I'd better not put into writing.
> These architects will probably have functions to retrieve a column from a
> record, maybe a function where you provide an id and the name of the column,
> which will be translated using dynamic sql. I've seen programs where three
> functions were called to retrieve 3 columns from a record. Underneath the
> complete record was fetched 3 times.
>> Reason being that the database cannot process the business rules efficiently nor can they effectively be managed.
> Is that so?
> My contention is that they care coming at it from a typical application
> perspective, not an ERP perspective.
>> I can understand workflow logic being externalized (aka Oracle Workflow), but the restricting stored procedures to CRUD operations
>> only... would seem to belittle the power of the Oracle database and what it has to offer.
> Since you are using Workslow, I suppose performance is no issue? The Oracle
> database is an awesome instrument, when looked after properly.
>> Mind you, these other individuals have primary backgrounds and experience with SQL Server. This may be where some of there
>> performance short sightedness may come from, you think ?
> Never underestimate an opponent, and it would be "their" shortsightedness.
>> Anyways, am I off my rocker about sayings its a blend, but that there definitely exist many opportunities for the business logic /
>> rules to exist in the database... and should.
>> BChase
>> (remove XX to contact)
> Quite right. Not that you are of your rocker, that is.

Some good points and reminds me of something else I forgot to mention. something I've often seen in applications that have the business rules in the applicaiton layer and none in the database (i.e. basic CRUD) is much much larger data retrievals/transfers. These systems tend to do little filtering of the data at the db level. instead, they retrieve large chunks of data and then filter it at the app level and then curse Oracle for being inefficient! It stuns me that people think something like Java sorting and filtering out data will be more efficient than doing it at the SQL level.


tcross (at) rapttech dot com dot au
Received on Mon Dec 14 2009 - 00:58:52 CST

Original text of this message