Skip to main content

Abstract

If you use partitioned tables as part of your application, it is likely, if not imperative, that you use partitioned indexes to complement the advantages gained by using table partitioning. Usually, having partitioned table and indexes go hand in hand—when there’s one, there’s usually both. This is common, but not essential. It is possible to have partitioned tables without partitioned indexes, and it is possible to have a non-partitioned table with partitioned indexes. There are several factors that affect the design of the database tables and indexes, including:

  • Application data loading requirements (DML)

  • Is it an OLTP system?

  • Is it a data warehouse?

  • Client query requirements

  • Data volume

  • Data purging requirements

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Darl Kuhn, Sam R. Alapati, and Bill Padfield

About this chapter

Cite this chapter

Kuhn, D., Alapati, S.R., Padfield, B. (2012). Partitioned Indexes. In: Expert Indexing in Oracle Database 11g. Apress. https://doi.org/10.1007/978-1-4302-3736-5_6

Download citation

Publish with us

Policies and ethics