Re: Code in the database or middle tier (the CLR controversy)

From: DA Morgan <damorgan_at_psoug.org>
Date: Wed, 01 Jun 2005 20:17:03 -0700
Message-ID: <1117682093.775003_at_yasure>


JRStern wrote:
> On 1 Jun 2005 03:28:41 -0700, SAN3141_at_netscape.net wrote:
>

>>There doesn't seem to be consensus about when to put code in the
>>database or in the middle tier. There was a long discussion about this
>>in an Oracle newsgroup (message ID:
>>ULcQb.466$KU5.37_at_nwrddc02.gnilink.net).

>
>
> Quite.
>
> Generally, the bulk of such discussion is between people who know only
> one tier and are trying to use it for everything.
>
>
>>IBM DB2 and Oracle are doing the same thing with the .NET CLR. Is this
>>a non-issue or are all three companies misguided?

>
>
> It's nice to have the option, but like with any power tool, if you
> don't know what it's for or how to use it, you may hurt yourself and
> others.
>
> One can indeed have long discussions about the architectural issues in
> theory and practice, but overall, I'd say it's a two steps forward,
> one step back. That nets (sic) out to a good thing.
>
> Josh

I think the main difference is that in the DB2 and Oracle worlds databases are generally under the control of DBAs that are formally trained and know how to say No! In the SQL Server world the vast majority of practitioners are home-schooled and have little if any format training on data bases and/or didn't come up from mainframe methodologies. They are far more likely to take the tool they know, VB, and use it to solve all problems with little understanding of the consequences.

-- 
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)
Received on Thu Jun 02 2005 - 05:17:03 CEST

Original text of this message