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: implications of merging 17 tables into 1...

Re: implications of merging 17 tables into 1...

From: William Robertson <williamr2019_at_googlemail.com>
Date: Wed, 27 Jun 2007 16:12:42 -0700
Message-ID: <1182985962.865570.34270@g4g2000hsf.googlegroups.com>


On Jun 27, 2:48 pm, nirav <shiva..._at_gmail.com> wrote:
> Here is one possible scenario that describes to an extent, the
> changes: Say that there are 5 tables and they are related by 4
> referential constraints (I am taking 4 as just one number, there could
> be more relations, but for example say 4). Now when we compress these
> 5 tables into one table, how is does the ref. integrity is taken care
> of? Does the data get exposed to some risk of corruption?
>
> Perhaps in the same table, there can be ref. keys referring to the
> same table (like mgr referring to empno in the emp table of scott
> schema) but in that case, when we do that for more than 10 relations,
> wouldn't that introduce much complexity?
> Can you please share your views on this.
>
> Thanks,
> Nirav

Being an optimist, I first wondered whether the 17 or 20 tables did actually belong in one table in the first place - say one table of sales data per month for th last 17 or 20 months, which the architect is proposing making into one (possibly partitioned) sales table with a "month" key.

However since you mention interrelated key constraints it is starting to look like an arbitrary bunching together of random stuff for no clear reason. Without any more clues to go on I'm still guessing though. If the architect mentions "persistence" you could be in trouble. Received on Wed Jun 27 2007 - 18:12:42 CDT

Original text of this message

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