Re: Oracle versus MS Sql Server

"Michael G. Schneider" <mgs_at_mgs-software.de> wrote in message news:9ratff$arm$00$1_at_news.t-online.com...
> "Howard J. Rogers" <howardjr_at_www.com> schrieb im Newsbeitrag
> news:3bd87efc$0$8345$afc38c87_at_news.optusnet.com.au...
>
> > I've got to say that your approach is doomed, and you'd be better off
> > writing applications for Access. I certainly wouldn't want to tune the
> mess
> > you, with your somewhat idiosyncratic approach, are almost inevitably
> going
> > to leave your DBAs.
>
>
> There is absolutely no reason for trying to offend me. I do know the
> difference between Access and Oracle. And when finishing my software
> development tasks there is no mess to be fixed by some DBA. If your
software
> developers make it necessary to create primary keys and constraints
> afterwards, you should think about changing software developers.
>
>
> As I already told, I am no Oracle DBA.I do not even know the course of
> education for a DBA. But if I am not completely wrong, "DBA" means
"Database
> Adminstration". Maybe me as a not natively English speaking person should
> not try to abstractely describe the word "Administration". But it
definitely
> does not sound like "Design" or "Development". Some of the subjects that
> immediately come to my mind when hearing "Database Administration" are...
>
> - install and update
> - intialization parameters
> - monitoring memory usage
> - monitoring performance
> - adjusting disk layout
> - configuring net structure
>
> These items certainly are not complete. But the other items mentioned in
> this thread (primary keys, constraints, cursors, ...) do sound like
> development issues to me.In the course of a project, these are decided by
me
> and are discussed with Database Designers.
>
> Michael G. Schneider
>
>
>

You are consistently trying to offend DBAs by stating 'I don't need your expertise'
In my formal function description 'designing the data model' is included. I am usually send to sites where they have the same attitude and policy as you have. Guess what I end up in? Invariably in messes, in applications developed by people with *NO* intimate knowledge of Oracle, sometimes even by people with *ABSOLUTELY NO* knowledge of Oracle, who think Oracle is the same as sqlserver and sybase.
You still seem to ignore the fact the choice of software influences the design.
So you are designing out of the blue, and at one point in time DBAs will get your product dumped on their doorstep.

I am quite aware most developers, and you seem to be a perfect and very example of it, look down on DBAs. I also know most DBAs look down on developers.
That's exactly because somehow people think their should be a chinese wall between DBAs and developers.
In fact, doing so, knowledge present in companies, will go down the drain, and projects will definitely cost much much more, as compared with the situation where the various competencies work together from the start.

I would love to hear success stories about your projects. I know firms will buy your software because in most cases there is no check from the DBA side as to the soundness of a project. So I am sure some people in the firms you sell to can tell disaster stories, as you simple wave away *any* argument.

Please don't expect I am going to respond to your newbie questions which will inevitably turn up soon.

Regards,

Sybrand Bakker
Senior Oracle DBA Received on Fri Oct 26 2001 - 01:50:57 CDT