Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec

Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec

From: HansF <News.Hans_at_telus.net>
Date: Sat, 18 Feb 2006 05:22:40 GMT
Message-Id: <pan.2006.02.18.05.22.38.677153@telus.net>


On Fri, 17 Feb 2006 18:25:41 -0800, Mark Townsend wrote:

>
> This one of the differences between Oracle and SQLServer. With Oracle, a
> coder does not have to be _as_ aware as to how to mitigate any
> limitations of the database server. They can do what they are good at -
> write business code. Let the database sort out transactions, isolation,
> concurrency problems etc.

Probably first time I've ever disagreed with you, Mark ...

I believe an Oracle coder has to be as much, or more aware, of the internals of the Oracle database to be able to justify NOT using the same database-limitation-work-arounds as a SQL Server coder needs.

I find the number of documents and the plethora of discussions hitting the limitations in SQL Server and workarounds makes management aware of the effort and they try to foist the same coding style on Oracle coders - generally with disasterous results.

I remember scratching my head when a SQL Server coder came up to me and asked how to get around a specific optomistic locking problem. I looked at him and said "the resolution is simple - switch to an engine for which you don't need to worry about it". Then I had to spend the next week explaining the Oracle internals. I had to justify the simpler method ...

-- 
Hans Forbrich                           
Canada-wide Oracle training and consulting
mailto: Fuzzy.GreyBeard_at_gmail.com   
*** Top posting [replies] guarantees I won't respond. ***
Received on Fri Feb 17 2006 - 23:22:40 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US