Along with partition elimination on query you can add following benefits of partitions. Most of these I have used in Datawarehouse and OLTP environments. Partition provide ability to run Web applications without downtime for data load. You can partition tables and using Exchange partition data get load. No downtime. We can separate History and Current data into partitions to reduce work load OLTP. To improve performance we can collapse multiple partitions into single partition. Example:12 month partition can collapse into single at the end of the year. Archive partitions can be moved to Readonly table space if needed. This way statistics intact at partition level. We can have compress/uncompressed partitions in table. Please note every thing based applications I have supported. It change base on your application. HTH Karth Sent from my IPhone > On Oct 28, 2013, at 9:58 AM, "Jeffrey Beckstrom" <JBECKSTROM@xxxxxxxxx> wrote: > > We are looking into the possibility of licensing the Partitioning option. My > understanding of partitioning is that it only helps when the optimizer can > eliminate partitions. Doesn't that mean that it is primarily of benefit when > accessing the tables via full table scans? In that case, the optimizer could > eliminate partitions from scanning. If, however, you are accessing the data > via an index\, would there be any benefit? > > Is my understanding of this correct? > > > > Jeffrey Beckstrom > Database Administrator > Greater Cleveland Regional Transit Authority > Information Systems > 1240 W. 6th Street > Cleveland, Ohio 44113 > > > > > > . > -- > //www.freelists.org/webpage/oracle-l > > -- //www.freelists.org/webpage/oracle-l