Re: compressed index and partition table?

Kate,

What do you mean large table? What is the volumn? If you table just under 100,000 rows, normal table is enough. If you use IOT, make sure your application will not update primary key frequently. I've never used IOT because I concerned the overhead if our application change primary key of tables.

Reid Lai

Kate Lin wrote:

> I just migrate database form oracle 7.3 to Oracle 8.1.6
>
> these is a large table:
> ARCH_RTU_DATA(
> A_RTUD_TAG_NAME VARCHAR2(24) NOT NULL,
> A_RTUD_TRUE_DATE DATE NOT NULL,
> .....
> )
>
> one composed primary key:
> ALTER TABLE ARCH_RTU_DATA ADD CONSTRAINT
> ARCH_RTU_DATA_PK PRIMARY KEY (A_RTUD_TAG_NAME,A_RTUD_TRUE_DATE)
> USING INDEX ....;
>
> another index:
>
> CREATE INDEX ARCH_RTU_DATA_TRUE_DATE_IDX ON ARCH_RTU_DATA
> (A_RTUD_TRUE_DATE) ...
>
> Two questions:
>
> 1. if i change the composed primary key to comressed index, can i get better
> performance besides the less space?
>
> create unique index arch_rtu_data_pk on
> arch_rtu_data(a_rtud_tag_name, a_rtud_true_date) compress 1
>
> 2. which field should be selected as a partition key if we want to use
> partition table?
>
> thanks a lot.
Received on Fri Aug 31 2001 - 02:25:52 CDT