21天学会APAP4的基础Day05.docVIP

Day?5 The Data Dictionary, Part 3 Chapter Objectives Understanding Table Indexes Displaying Indexes Considerations When Creating an Index Creating a Secondary Index Deleting a Secondary Index Determining Which Index Is Used Displaying Technical Settings Data Class Size Category Displaying the Number of Extents Allocated to a Table Buffering a Table Summary QA Workshop Quiz Exercise 1 Chapter Objectives After you complete this chapter, you should be able to: Create and use secondary indexes appropriately Set up the technical attributes for transparent tables Set up buffering for tables Understanding Table Indexes An index is an efficiency mechanism for quickly finding rows within a table. It is needed because data is stored in a table in the order in which it was added (the order of arrival). Picture yourself ripping all the pages out of this book and then throwing them into the air and mixing them all up. You then gather them into a stack without regard to any sort of order. If you were to look for a single page number within that stack, how would you do it? Some people might just hunt and peck though the stack hoping to find it. Im sure that most would soon give up and then turn the pages one by one. Obviously, this job would be easier if the pages were all back in order. With the pages in order, you could start somewhere in the middle and knowing which way to turn, you could quickly zero in on the page you want. Imagine that you have now put the pages back in order. Picking up the newly ordered book, perhaps you begin to look for the page that describes SE16. Where do you look? You dont know the page number, so you look in the index. The index contains the most important words sorted in alphabetical order. You quickly locate SE16 in the index and obtain a page number. Using that, search through the book to find that page. To create an index, the publisher duplicates important information and then sorts it, placing it at the end of the book