We were asked, not too long ago, to create one Oracle8i database with only
*one* table with some 700+ columns. While at it, the consultant (hired by
end user dept) also suggested that we make it an IOT using an LMT, and since
the table will never grow over 1GB, asked if there was a way to put it
it's all in the buzzwords, obviously :)
--- Deshpande, Kirti [EMAIL PROTECTED] wrote:
We were asked, not too long ago, to create one Oracle8i database with
only
*one* table with some 700+ columns. While at it, the consultant
(hired by
end user dept) also suggested that we make it an IOT
But the DOCUMENTATION says
8-0
April Wells
Oracle DBA
Keep yourself well oiled with life, laughter, new ideas and action.
Otherwise you will rust out. _Anonymous
-Original Message-
Sent: Friday, October 11, 2002 10:20 AM
To: Multiple recipients of list ORACLE-L
it's all in the
I wanted to take a picture with him.
.. and take him out to lunch to learn from his experience ... ;-)
but it turned out he lasted only for less than a week... ;)
(Some developers he was working with knew a bit more Oracle than him)
- Kirti
-Original Message-
Sent: Friday,
Mark...
If this were the MOST serious design flaw in the whole mess, I wouldn't care
so much. There is a point where you just shut up (gee, I have been TOLD to
do that in meetings) and wait till it breaks (or worse, one of our clients
buys it and we have to TRY to implement). I am the funny
April,
What can I say? Ouch! I feel your pain. I've been trapped in some
pretty ridiculous situations too. (Though, I think you have me beat! A
37 column primary key?? Really??) Well, you at least seem to have the
proper attitude. ;-) Without a sense of humor, I'm afraid you'd go
insane in
Hi Dick,
I have to disagree with you here. Particularly in the case where this
sequence will see any sort of concurrency, from multiple concurrent
sessions accessing it. This is due to the serialization on the SQ
enqueue. This will cause far worse scalability issues than any I/O.
Not that
