Re: Oracle versus MS Sql Server

Hi Jim,

I do understand your point, although I do not quite agree with it. Of course I do know anything (not really anything) about SQL and OLE/DB. And I think this is enough for creating a great application. For example, I do not know anything about optimizing the tablespace layout or about caching in the database. And I think this knowledge is absolutely not necessary for me. For an application database subjects as "normalized tables", "foreign key relationsships", "constraints", "indexes" are more important.

"Poorly designed applications" as you call them, will always have problems. But in my opinion an application can be perfectly designed on the basis of SQL (either MS or Oracle) and the application code.

About 40% of my applications have been targeted at both databases, Oracle and SQL Server. Certainly the SQL is different, but I did not need any specific DBA know-how for developing these application. That knowledge may be with one or the other DBA.

Michael G. Schneider

"Jim Kennedy" <kennedy-family_at_home.com> schrieb im Newsbeitrag news:lG5A7.30443$Zb.13770728_at_news1.sttln1.wa.home.com...
> Michael,
> If all you want to do is set Oracle up so you can write an application
etc.
> Then certainly the 8i series and later is basically run setup.exe.
> (Assuming you haven't installed it a bunch of times before hand.). On the
> other hand if you want to use all the administrative bells and whistles
etc.
> then that really is not in the application developer domain. Yes, Oracle
> could make those things easier and constantly strives to do so (and does),
> but at some level if you want to muck with administrative stuff you are
> going to have to either learn it, get assistance from someone, or get
> someone else to do it.
>
> It is rather naive though to developed an application and not really have
> someone with DBA skills available. (It is possible to be both, but we are
> talking quite a lot of experience which most people don't have in both
> domains.) Being someone who has extensive experience in both "camps" I
have
> seen time and time again application developers make the same mistakes
over
> and over again out of ignorance (not stupidity or laziness, just lack of
> database experience). Poorly designed applications that use a database,
and
> there are a lot out there often cannot be fixed by the DBA no matter how
> competent they are. Performance and scalability are part of everyone's
job
> at every step and not something to try to tack on later.
> Jim
Received on Sat Oct 20 2001 - 01:53:51 CDT