Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Article about supposed "murky" future for Oracle
"Thomas Kyte" <thomas.kyte_at_oracle.com> wrote
>to add an index to prevent queries from deadlocking
>who'd have thunk it.
^^^^^^^^^^^^^^^^^^^
Any DBA with some experience in SQLS. It is well documented in SQLS manual that lack of index can result in dead lock. I can take it off line on what happened in that case. Creation of appropriate index is the domain of DBA and I think it is true in any database.
> and what if the query plan decides for whatever reason
> "index isn't the right thing".
The keywords are "what if" and "whatever reason". Are you by any chance speaking from Oracle experience :-)
> And this in read committed - a
> non-consistent level of isolation in those databases.
Not every query requires a read-consistent state.
> thats all. with multi-versioning, we just don't even think about
> that.
big deal. In every database there will be some issues which, to paraphrase
you "who would have thunk it".
I don't work with Oracle technology. But a cursory glance in this group tells me there
are plenty of who-wud-have-thunk-it issues. Check this. http://tinyurl.com/2dz8o
Someone had a Orrible time with a query and it turns out that some obscure
parameter _push_join_union_view should be set to TRUE for better performance.
I am not trashing Oracle here. All I want to say is that in every database
some work is involved to get things done.
Received on Thu Apr 01 2004 - 16:31:56 CST
![]() |
![]() |