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: Tony Rogerson <tonyrogerson_at_sqlserverfaq.com>
Date: Sat, 18 Feb 2006 10:36:20 -0000
Message-ID: <dt6tag$m8n$1$8302bc10@news.demon.co.uk>


> 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.

Having coded using both SQL Server and Oracle, all though the Oracle was version 7 or whatever was out in 1993(ish) and Oracle Glue I can tell you that the coder does need to worry about such things.

The majority of applications use the default locking behaviour in SQL Server and have NO problems, the coder doesn't need to change the isolation level, mind you - its good to have an understanding of the ANSI standard isolation levels; depending on your application you might need SERIALIZABLE. But that's an ANSI thing, not SQL Server. SQL Server does make it easy to change locking behaviour on the fly per connection with a simple SET statement.

> Coders need to know how to write business code, and also how to write this
> code to avoid isolation problems, deadlocks etc.

Please, you are not trying to tell me you don't get deadlocks in Oracle.

Deadlocks and concurrency are common traits to any database system and they need to be coded for in the application.

The application needs to cater for when a deadlock occurs, do they re-try or fail.

The application needs to cater for concurrency, the row you've just modified on your disconnected browser windows - when the user clicks update, can I guarentee the row hasn't been modified by another user, please don't insult my intelligence by telling me the database deals with that, it might do in a batch of SQL running in a transaction - but in a disconnected browser model - i don't think so.

-- 
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials


"Mark Townsend" <markbtownsend_at_comcast.net> wrote in message 
news:43F685A5.10405_at_comcast.net...

> Galen Boyer wrote:
>
>>>
>>>Does work though and scales.
>>
>>
>> As long as one is congnizant of the resources being used and coding
>> accordingly.
>
> 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.
>
> SQLServer is much more demanding on coders. Coders need to know how to
> write business code, and also how to write this code to avoid isolation
> problems, deadlocks etc. Note that Tony, both as a SQLServer MVP, and a
> consultant, presumably makes a healthy living from having this required
> knowledge.
>
Received on Sat Feb 18 2006 - 04:36:20 CST

Original text of this message

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