Abstract
During the translation from the logical design to the physical design, you must make four kinds of decisions. First, for each table, you have to decide not only whether you should use a heap table, a cluster, or an index-organized table, but also whether it has to be partitioned. Second, you must consider whether you should utilize redundant access structures such as indexes and materialized views. Third, you have to decide how to implement the constraints (not whether you have to implement them). Fourth, you have to decide how data will be stored in blocks, including the order of the columns, what datatypes are to be used, how many rows per block should be stored, or whether compression should be activated. This chapter focuses on the fourth topic only. For information about the others, especially the first two, refer to Chapters 13, 14, and 15.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
SELECT statements modify blocks in two situations: first, when the FOR UPDATE option is specified, and second, when deferred block cleanout occurs.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Christian Antognini
About this chapter
Cite this chapter
Antognini, C. (2014). Optimizing the Physical Design. In: Troubleshooting Oracle Performance. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-5759-2_16
Download citation
DOI: https://doi.org/10.1007/978-1-4302-5759-2_16
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-5758-5
Online ISBN: 978-1-4302-5759-2
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books