Browse Prior Art Database

Enhance for subset index include depending on policy

IP.com Disclosure Number: IPCOM000245353D
Publication Date: 2016-Mar-03
Document File: 3 page(s) / 74K

Publishing Venue

The IP.com Prior Art Database

Abstract

An index is an ordered set of pointers to the data in a database table. The index is stored separately from the table. Each index is based on the values of data in one or more columns of a table. After you create an index, database maintains the index, but you can perform necessary maintenance such as reorganizing it or recovering the index. Indexes take up physical storage in index spaces. Each index occupies its own index space. The main purposes of indexes are to improve performance. After accessing index page and also need to access data page for record values. Currently, we would like to introduce a kind of subset index include basing on policy, if the big index is so big which might affect the performance. As shown as below, the left one is the full index for the table, there might be some of the hot keys which might be hit frequently and we could issue some values would be accessed more efficient such as VIP user, when these keys are switched out of cache frequently, we could like to copy or move these keys into index leaf pages during reorganizing the storage. Other than that, we also move the record might be hit to the leaf pages to issue index only to get higher performance. When the query uses the index to get record

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Enhance for subset index include depending on policy

An index is an ordered set of pointers to the data in a database table. The index is stored separately from the table. Each index is based on the values of data in one or more columns of a table. After you create an index, database maintains the index, but you can perform necessary maintenance such as reorganizing it or recovering the index. Indexes take up physical storage in index spaces. Each index occupies its own index space. The main purposes of indexes are to improve performance. After accessing index page and also need to access data page for record values.

Currently, we would like to introduce a kind of subset index include basing on policy, if the big index is so big which might affect the performance. As shown as below, the left one is the full index for the table, there might be some of the hot keys which might be hit frequently and we could issue some values would be accessed more efficient such as VIP user, when these keys are switched out of cache frequently, we could like to copy or move these keys into index leaf pages during reorganizing the storage. Other than that, we also move the record might be hit to the leaf pages to issue index only to get higher performance. When the query uses the index to get record

The index structure of the index is that the non-index pages should only contain the key value, and the leaf page would contain the columns which is most combined with these key values.

The following is the detail process.

1



Page 0...