Indexing Rules of Thumb Index Selection Decisions

Indexing Rules of Thumb : Index every primary key and most foreign keys in the database. Attributes frequently referenced in SQL WHERE clauses are potentially good candidates for an index. Use 本文来源[email protected]搞@^&代*@码)网9a B+tree index for bothequality and range quer

Indexing Rules of Thumb :

Index every primary key and most foreign keys in the database.

Attributes frequently referenced in SQL WHERE clauses are potentially
good candidates for an index.

Use a B+tree index for bothequality and range queries.

Choose carefully one clusteredindex for each table.

Avoid or remove redundantindexes.

Add indexes only whenabsolutely necessary.

Add or delete index columns forcomposite indexes to improve performance.
Do not alter primary key columns.

Use attributes for indexes withcaution when they are frequently updated.

Keep up index maintenance on aregular basis; drop indexes only when
they are clearly hurting performance.

Avoid extremes in index cardinality and value distribution.

Covering indexes (index only) are useful, but often overused.

Use bitmap indexes for high-volume data, especially in datawarehouses.

Index Selection Decisions :

Does this table require an index or not, and if so which search
key should I build an index on?

When do I need multi-attribute(composite) search keys, and
which ones should I choose?

Should I usea dense or sparse index?

When can I use a coveringindex?

Should I create a clusteredindex?

Is an index still preferredwhen updates are taken into
account? What are the tradeoffs between queries and updates for each indexchosen?

How do I know I made the rightindexing choice?

—

，网站空间，网站空间，香港空间

搞代码网（gaodaima.com）提供的所有资源部分来自互联网，如果有侵犯您的版权或其他权益，请说明详细缘由并提供版权或权益证明然后发送到邮箱[email protected]‍，我们会在看到邮件的第一时间内为您处理，或直接联系QQ：872152909。本网站采用BY-NC-SA协议进行授权
转载请注明原文链接：Indexing Rules of Thumb Index Selection Decisions

Hi，您需要填写昵称和邮箱！