My New developerWorks Article: Why Low-Cardinality Indexes Negatively Impact Performance

Posted by

My second developerWorks article has been published! This is a bit of a technical deep dive into a question that was running around my head earlier in the year. Give it a read and let me know what you think!

Low cardinality indexes can be bad for performance. But, why? There are many best practices like this that DBAs hear and follow but don’t always understand the reason behind. This article empowers DBAs to understand the logic behind why low cardinality indexes can be bad for performance or cause erratic performance. The topics this article covers include B-tree indexes, understanding index cardinality, hypothetical examples of the effects of low cardinality indexes, a real-world example of the effects of a low cardinality index, and tips on how to identify low cardinality indexes and reduce their impact on performance.

Figure 4 appears to be missing for some reason. I have notified developerWorks and they are fixing it. In different colors, it looks something like this:

Lead Database Administrator
Ember is always curious and thrives on change. Working in IT provides a lot of that change, but after 18 years developing a top-level expertise on Db2 for mid-range servers and more than 7 years blogging about it, Ember is hungry for new challenges and looks to expand her skill set to the Data Engineering role for Data Science. With in-depth SQL and RDBMS knowledge, Ember shares both posts about her core skill set and her journey into Data Science. Ember lives in Denver and work from home

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.