Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

SQL 102 – CLUSTERED vs. NONCLUSTERED Indexes

Posted on January 9, 2009February 9, 2011 by slowder

Previously, I covered the basics of creating an index using CREATE INDEX.  Today, I’m going to dig a little deeper.  I’d like to teach you the difference in an CLUSTERED versus a NONCLUSTERED index.  If you learn nothing else, know that a CLUSTERED INDEX physically orders the table, a NONCLUSTERED INDEX creates another “table” and orders that, each row of that “table” will point back to a record in the table you’re indexing.

CLUSTERED INDEX

CREATE CLUSTERED INDEX cix_tableName__columnName
ON tableName (columnName)

Like I was explaining before a CLUSTERED INDEX orders the corresponding rows in the table in the logical order of the index.  In my previous T-SQL statement tableName will be physically ordered by columnName.  This is like permanently applying an ORDER BY statement on this table.  Another, Microsoft, way of saying this is the bottom, or leaf, level of the clustered index contains the actual data rows of the table.

Please note: a TABLE or VIEW can only have one CLUSTERED INDEX at a time.  Think about it.  If you were going to index a table of contacts, you can’t sort by the first name and the last name at the same time.  One ordering would undo the other!  If you want to order by one column and then the other column you can use multiple columns in your CREATE INDEX statement.

CREATE CLUSTERED INDEX cix_contact__lastname_firstName
ON contact (lastname, firstName)

This would order everything like a phone book.  by last name and then first name.  For more information, see Clustered Index Structures.  Oh, and before I forget, NONCLUSTERED is the default type of indexed created.  If you don’t explicity call for a CLUSTERED INDEX, you’re not getting one.  The DBA in me thinks there ought to be another rule… always be explicit in your T-SQL, you slackers! (I know slackers isn’t an explicit word, but you get the point, right?)

NONCLUSTERED INDEX

CREATE [NONCLUSTERED] INDEX ix_tableName__columnName
ON tableName (columnName)

Again, technically the NONCLUSTERED keyword is not required by the parser, but it’s required by me.  By running this statement you are Creating an index that specifies the logical ordering of a table.  Your index is physically independent of the table you are indexing.  In this case, Microsoft might say the leaf level of the NONCLUSTERED INDEX contains a pointer to the row it refers to.  As I mentioned before, if you don’t explicitly call for a NONCLUSTERED INDEX, you get one anyway.

For more information, see Nonclustered Index Structures.

That’s the difference between these two types of indexes.  Don’t worry, I’ll be building on this topic too.  It gets more complicated from here!

If you have any questions, send them in… I’m here to help!

Leave a Reply Cancel reply

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

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme