there are 2 ways partitioning can improve performance
- partition pruning during query, so your query need only read part
of the table
- local indexes, which reduce maintenace work during insert, because
only one index partition need to be updated which is smaller
and better fitting into cache
(you need to partition historical, to splitt the data of old partition
into seperate partition, very good approach with 9.2 compress
attribute )
"Michael Wu" <kuohwa_at_ms21.hinet.net> schrieb im Newsbeitrag
news:atfigq$84i_at_netnews.hinet.net...
> Dear All,
>
> I partition my order table into 4 partition and use range partition,
> I split it into only 1 tablespace, because the db only has 1 external disk
> which have 12 disks with 1 raid5 set.
>
> After I create a new table and insert old order data into new table, I
still
> can not fell any speed up from the new table,
> Did I lose some thing to setting? or the partition only suit for very
large
> such hundred of GB but not MB?
>
> Please give me a hint.
>
> Thank You Very Much.
>
> Michael Wu
> kuohwa_at_ms21.hinet.net
>
>
>
>
Received on Sun Dec 15 2002 - 07:15:42 CST
