Re: Optimized Indexing for a Schedule Table
I should also point some things out about the data if it helps
#1 Rows get updated quite often so there is lots of index churn
#2 Rows get inserted much less often
#3 Prio=0 means highest priority
#4 Typical usage patterns tend to bring the data in order when sorted on only the fire_time (and excluding priority) except for rows that never fire
#5 The prio column values are skews such that there are many more rows that have a high valued 'prio' entry
#6 There are quite a few rows with low priority (large prio) that never get updated because they are never "reached". Higher priority items tend to block them so they have fire_time values far in the past.
Subject
Views
Written By
Posted
3742
November 23, 2010 11:58PM
1217
November 25, 2010 02:35PM
1838
November 25, 2010 10:47PM
Re: Optimized Indexing for a Schedule Table
1278
November 25, 2010 11:05PM
1725
November 26, 2010 01:42PM
1355
November 26, 2010 11:36PM
1447
November 27, 2010 01:31PM
1362
November 27, 2010 02:44PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.