Re: Table Design

De-normalizing really depends on how you are going to get data out of the DB. If you need to print hourly reports from two tables, you might want to merge them.

Fully normalized is usually very fast at transactions, but slower at reporting across the tables.

If you have two or three standard reports, you could build de-normed tables just for those reports.

Open ended question really...

JKL "SATYA PAL" <spgangwar_at_yahoo.com> wrote in message news:a7b8a58b.0106110412.4661624a_at_posting.google.com...
> Hi There,
>
> We are in the process of designing a database for a big application
> and so far we have designed all the tables almost fully normalized.
>
> There are lot of tables which are having one to one relationships and
> that to mandatory (i.e. parent and child will always have the
> records). To reduce the joins, should we merge these tables into one
> instead of two or more tables (one to one). Any idea/suggestion ?
>
> Most of the tables which have very minimal Insert/update/delete
> operations but the mostly used to fetch the data, would there by any
> performance impact on these tables if there are more than 120 columns
> in the tables ? If so then these should be logically divided into
> multiple tables with one to one relationship.
>
> I appreciate if someone can help me on this topic.
>
> Regards
> Satya
Received on Wed Jun 13 2001 - 22:01:26 CEST