network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | Feb 12 at 15:10 | |
| stats | profile views | 9 |
|
Jan 31 |
asked | How to select only the number from “show global status like 'Com_insert';” |
|
Apr 9 |
comment |
Making the Oracle optimizer use a virtual column to find out about a partition Thanks APC. The reason I don't want to use subpartition is because of my text index. I don't want to have a domain text index because I don't want to rebuild it when I split my max partition. I was trying to come up with an alternative by using this virtual column. |
|
Apr 9 |
asked | What is the performance difference between local text index and domain text index in oracle? |
|
Apr 9 |
comment |
Making the Oracle optimizer use a virtual column to find out about a partition It only scan partitions that has start_date_value > 20120201300.23452 |
|
Apr 9 |
accepted | Making the Oracle optimizer use a virtual column to find out about a partition |
|
Apr 9 |
comment |
Making the Oracle optimizer use a virtual column to find out about a partition thank you for pointing out my mistake in calculation. In this test, I want to know if Oracle is smart enough to figure out that it needs to use the virtual column to go to a subset of partitions instead of going to every single partition. I have more than 3500 partitions and it really hurt performance doing that way. Can we influence the query plan somehow to make it use the virtual column even though we don't specify it? |
|
Apr 9 |
awarded | Editor |
|
Apr 9 |
revised |
Making the Oracle optimizer use a virtual column to find out about a partition added 1 characters in body |
|
Apr 9 |
comment |
Making the Oracle optimizer use a virtual column to find out about a partition So it should only scan partition that has START_DATE_VALUE > 20120201300.23452 only. |
|
Apr 8 |
asked | Making the Oracle optimizer use a virtual column to find out about a partition |
|
Jan 16 |
awarded | Supporter |
|
Jan 16 |
accepted | oracle local partition index |
|
Jan 16 |
asked | oracle local partition index |
|
Jan 13 |
accepted | oracle global index vs local index on a partitioned table |
|
Jan 13 |
comment |
oracle global index vs local index on a partitioned table I partition my data to be the most common query for that time (30 days). And you are right. I don't need to index on create_time any more. There is no benefit. Just to be clear, i also have another index (Create_Time, ColumnA, ColumnB). Now with partition, i only need to do local index on (ColumnA, Column B)? |
|
Jan 12 |
awarded | Scholar |
|
Jan 12 |
accepted | Estimate space left in Oracle |
|
Jan 12 |
asked | oracle global index vs local index on a partitioned table |
|
Jan 12 |
awarded | Student |
|
Jan 6 |
asked | Estimate space left in Oracle |
