Re: Newbie's Oracle 9i impression: it sucks

From: SQLJoe <sqljoe_at_aol.com>
Date: 21 May 2002 18:25:02 GMT
Message-ID: <20020521142502.02455.00000104@mb-mu.aol.com>

Howard wrote:

>Actually, which of the words 'unless you force the issue' didn't you
>understand? I'm sure that inserted and deleted tables can be created to
>allow you to see the data before it is committed. That wasn't my point. What
>happens when you have a single emp table, I do an update and you do a
>select? You hang, that's what. Sure you can "deal" with the issue. But by
>DEFAULT, you hang. Which is not the case in Oracle at all. As I said: the
>issue with MS SQL Server and most other database products out there is
>concurrency. By default, out of the box, without effort, they lack it and
>Oracle doesn't.
>

You can manually set the transaction isolation levels in MS SQL. So YES, you CAN allow MS SQL to read rows when there is an update happening on the same row. You use the "Read Uncomitted" isolation level for this.

Jinsoo
MCDBA, MCSD, MCSE+I Received on Tue May 21 2002 - 13:25:02 CDT