Re: Table Design question

Oracle uses only 1 byte to store empty fields. Blank fields at the end of a row do not even use a byte. ( or just 1 or 2 for them all )
So i recommend adding the details to the main table putting the most used set first and then next most used set and so on.

If you were updating the table this would be bad becasue you would need a very high pctfree to accomadate expansion of all the detail fields. But since you said this is a query only table create it with a pctfree of 0 which will allow more rows per block.

Barry Evans
Promaxis Systems Inc

Gennaro Napolitano wrote in message <38BAA9CA.98C0FB8B_at_italdata.it>...
>Hy folks
>
>I am planning a DB Schema, and I need some hints.
>
>At the moment I have the following scenario:
>
>Table "common_target" with some information common to various targets
>(location, tel, fax and so on. circa 10 columns), and 5 detail tables
>describing the specific target (common_target_id plus 4 or 5 additional
>columns).
>
>These table are fullfilled just one time and then updated every 3
>months, but they will be queried very frequently.
>
>I thought to change the schema collecting all the info in just one
>table, and create view to handle the target specific information.
>
>My primary need is the query performance, what do you think about my
>change proposal?
>
>Thanks a lot in advance
>
>Ciao Gennaro
>
>
>
Received on Tue Feb 29 2000 - 00:00:00 CST