Re: When to use partitioned tables ?

On Thu, 28 Jun 2001 07:23:58 GMT, "Francesco Marchioni" <fmarchioni_at_libero.it> wrote:

>Hi all,
>I'm studying how to partition a table. I wonder what are
>the standards about this: for example how many records
>you need to have in your Table in order to start thinking
>about partitioning ? I speak about an ordinary sized table...
>I just want an advice if 10.000 records are worth partitioning
>or you should have about 1.000.000 in order to outweigh the
>cost of partitioning (I think that there must be some overhead
>in your query when you use a partitioned a table)
>Thanks
>Francesco
>
>
>

Hi Francesco,

Partitioning is especially useful on huge, high-volatile tables ( > 1 mill. rows).

The benefits of partitioning are first of all administrative, allowing you to subdivide operations on your huge tables into more managable chunks. I.e., you can spread your data across multiple tablespaces and make DBA-operations on one set of data ( = one partition ) without affecting the others. You can use partitioned indexes on a partitioned table which adds more flexibility to the adm. of the indexing.

If you don't need these administrative benefits, you probably don't need to partition your table.

Regards,
Kenneth Koenraadt
Systems Consultant
Oracle DBA
plovmand@<no-spam>hotmail.com Received on Sat Jun 30 2001 - 11:34:12 CDT