Re: cost of having MANY tables

Hi,

 You will need more SGA memory to cache parsed statements (oviously, there are going to be a lot of different statements).  You also need more memory to cache the data dictionary.

 Maintainance is going to become difficult - you have to take care of lots of indexes, constraints etc. Performance Tuning is going to be a headache too.

 Parsing will become more expensive, you need more CPU horsepower.

 Joins, selects should not be that different (apart from the not data- dependend overhead described above.) - this tends to be bound on disk i/o.

HTH Karsten

In article <384458AE.75EAEC11_at_averstar.com>,   Steve Parker <sparker_at_averstar.com> wrote:
> Can someone please give me a run down of the costs of having a HUGE
> amount of tables (each being pretty small) as opposed to having fewer
> tables that are bigger?
>
> i.e., space, speed (individual accesses and joins)
>
> any help is much appreciated
> parker
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Dec 02 1999 - 05:51:29 CST