Re: .NET stored procedures

On Jan 15, 2:40 pm, "Michael O'Shea" <michael.os..._at_tessella.com> wrote:
> HansF wrote:
> > Unfortunately, the majority of .Net, C#, Java (and even many PL/SQL)
> > developers seem to prefer doing the data manipulation in the app code
> > instead of the database. As a result, the majority of apps I've seen tend
> > to run worse than they should.
>
> > If it's performance you want, make sure you understand the tools, and
> > especially the Oracle database mechanics, before coding. If you
> > haven't done so, please Read Tom Kyte's books.I couldn't agree more Hans, and if I may deviate slightly off topic,
> the following article was distributed internally recently.
>
> http://www.addsimplicity.com.nyud.net:8080/downloads/eBaySDForum2006-...
>
> It outlines the eBay architecture with Oracle as the DBMS. Page 22
> "Scaling the Data Tier: Minimize DB Resources" writes the following:
>
> * No business logic in database
> - No stored procedures
> - Only very simple triggers (default value population)
> * Move CPU-intensive work to applications
> - Referential Integrity
> - Joins
> - Sorting
>
> I'm sure there is something contentious there.
>
> Mike
>
> TESSELLA Michael.OS..._at_tessella.com
> __/__/__/ Tessella Support Services plc
> __/__/__/ 3 Vineyard Chambers, ABINGDON, OX14 3PX, England
> __/__/__/ Tel: (44)(0)1235-555511 Fax: (44)(0)1235-553301www.tessella.com Registered in England No. 1466429

Not contentious.
Just the usual utter bullshit which demonstrates the 'architects' don't have any clue with respect to Oracle.
It outlines all policies of which Tom Kyte explains will make your database and your application utterly unscalable.

-- 
Sybrand Bakker
Senior Oracle DBA