network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 7 months |
| seen | Oct 17 '12 at 8:34 | |
| stats | profile views | 0 |
|
Sep 25 |
awarded | Student |
|
Sep 24 |
comment |
INDEX Creation Advice Oracle @a_horse_with_no_name, My create table statement is something similar to the one below. My question would be if the performance of a query which has both the (interva_date,person_id) be good if a hash sub partition is created for person_id to the range index that is created in this script. CREATE TABLE interval_date ( person_id NUMBER(5) NOT NULL, last_name VARCHAR2(30), dob DATE) PARTITION BY RANGE (dob) INTERVAL (NUMTOYMINTERVAL(1,'MONTH')) STORE IN (uwdata) ( PARTITION p1 VALUES LESS THAN (TO_DATE('2008-03-15','YYYY-MM-DD'))); |
|
Sep 24 |
comment |
INDEX Creation Advice Oracle @JustinCave: There is an existing Index on the date column(range partitioned). I would like to create a combined index on date and the unique id column. When i try to create a combined I hit a ORA:1652 as I run out of disk space. From what i read, I would not able to add a new column to an existing index.When i meant index type i meant local vs global. Will it actually solve the space problem? What would be the best choice of index when a user queries on both the unique id and date time. Should i create a local index on the partitions? |
|
Sep 24 |
asked | INDEX Creation Advice Oracle |
