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

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Re[2]: Re[2]:Upgrading Oracle

RE: Re[2]: Re[2]:Upgrading Oracle

From: Weaver, Walt <wweaver_at_rightnow.com>
Date: Wed, 25 Oct 2000 07:50:15 -0600
Message-Id: <10660.120161@fatcity.com>


FWIW, don't feel like the Lone Ranger, Rachel. I'm fighting the same battle here with our developers...

--Walt Weaver

  Bozeman, Montana, USA

-----Original Message-----

From: Rachel Carmichael [mailto:carmichr_at_hotmail.com] Sent: Tuesday, October 24, 2000 10:06 PM To: Multiple recipients of list ORACLE-L Subject: Re: Re[2]: Re[2]:Upgrading Oracle

oh that was minor compared to today's rant... a third party product that denormalizes tables because their "experts" told them that if you have more than 4 tables in a join performance suffers significantly.

So instead of a parent table with a child table that contains one row for each option selected, I have ONE table with a column for every possible option, and a Y/N switch for each one. AND just to make it even more interesting, if you want to add a new option, the product automatically adds

a new column to the table. We expect to have something like 5-15 million rows in that table. And we will do selections for mass emails based on each of those columns. Which I can't index, so we will do multiple full table scans on a table way too large to pin into the buffer pool.

I managed not to foam at the mouth. And made sure that EVERYONE in that meeting knew that I thought that this design was going to cause us major performance problems that I could not necessarily do DBA magic to remove. Received on Wed Oct 25 2000 - 08:50:15 CDT

Original text of this message

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