InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 00:12:57 GMT20http://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspxDavid,This series is absolutely top draw and this internal index stuff is great. As they say a picture is worth a thousand words, these diagrams and walkthrough you give explains it all in simple and laymans terms.rgdsrobinThu, 08 Mar 2012 05:12:01 GMTrobinrai3http://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspxThere's just so much information in the this article and discussion!Please keep up the good work.Many books don't expose the level of detail presented here and leave us wondering how that really works from the inside.Thank you very much David (and Gail for the additional info and link).Fri, 20 Jan 2012 14:16:15 GMTcodebyohttp://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspx[quote][b]patrickmcginnis59 (1/20/2012)[/b][hr]Thanks! I didn't even consider deletes. I'll have to buy some popcorn and watch the movie![/quote]Not a movie. One of the MCM videos. That particular one is about 40 minutes long and all about index internalsp.s. not just deletes, any modification that has to change the data in the index leafFri, 20 Jan 2012 07:41:32 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspx[quote][b]GilaMonster (1/20/2012)[/b][hr][quote][b]patrickmcginnis59 (1/20/2012)[/b][hr]Whats the downside of having duplicate rows in nonleaf nodes? Aren't they still going to point to the correct child nodes that they're the parent of?[/quote]Yes, they will, however it can be more work when modifying or deleting the rows. Imagine an index on gender and a row is deleted. That row needs to be located in the nonclustered index to be removed (from the leaf). If all we had at the intermediate levels was the gender, SQL would have to scan half the index to find the row that it needs to remove. If the index rows are unique (from the clustered key or RID), SQL can just navigate straight to the row it need to remove.[url]http://technet.microsoft.com/en-us/sqlserver/gg508878.aspx[/url] (about 24 minutes in)[/quote]Thanks! I didn't even consider deletes. I'll have to buy some popcorn and watch the movie!Fri, 20 Jan 2012 07:33:12 GMTpatrickmcginnis59http://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspx[quote][b]patrickmcginnis59 (1/20/2012)[/b][hr]Whats the downside of having duplicate rows in nonleaf nodes? Aren't they still going to point to the correct child nodes that they're the parent of?[/quote]Yes, they will, however it can be more work when modifying or deleting the rows. Imagine an index on gender and a row is deleted. That row needs to be located in the nonclustered index to be removed (from the leaf). If all we had at the intermediate levels was the gender, SQL would have to scan half the index to find the row that it needs to remove. If the index rows are unique (from the clustered key or RID), SQL can just navigate straight to the row it need to remove.[url]http://technet.microsoft.com/en-us/sqlserver/gg508878.aspx[/url] (about 24 minutes in)Fri, 20 Jan 2012 07:03:22 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspx[quote][b]GilaMonster (1/20/2012)[/b][hr]Just one correction:[quote]Non-leaf level entries contain only index key columns and the pointer to a lower level page. Included columns only exist in the leaf level entries; they are not carried in the non-leaf level entries.[/quote]Non-leaf entries of a nonclustered index contain the index key columns, a pointer to the page below and, if the index has not been declared as unique, it will also contain the clustered index key or RID (depending whether the base table is a heap or clustered index). This ensures that there are never complete duplicate rows in the upper level of a nonclustered index[/quote]Interesting! Whats the downside of having duplicate rows in nonleaf nodes? Aren't they still going to point to the correct child nodes that they're the parent of?Fri, 20 Jan 2012 06:32:24 GMTpatrickmcginnis59http://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspxJust one correction:[quote]Non-leaf level entries contain only index key columns and the pointer to a lower level page. Included columns only exist in the leaf level entries; they are not carried in the non-leaf level entries.[/quote]Non-leaf entries of a nonclustered index contain the index key columns, a pointer to the page below and, if the index has not been declared as unique, it will also contain the clustered index key or RID (depending whether the base table is a heap or clustered index). This ensures that there are never complete duplicate rows in the upper level of a nonclustered indexFri, 20 Jan 2012 01:49:12 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspxThank you very much! Finally finished going through all 10 steps little by little and been worth every second! Looking forward to the rest of the them.Thu, 19 May 2011 14:53:55 GMTj-ghttp://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspxAm dancing as fast as I can.Hope to have it all into Kalen (the editor) shortly.Dave.Tue, 05 Apr 2011 11:48:06 GMTDavid Duranthttp://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspxEnjoying the series. Looking forward to the rest of them. Hurry hurry lol.:-)Tue, 05 Apr 2011 10:16:17 GMTChristopher Teixeirahttp://www.sqlservercentral.com/Forums/Topic1085227-2904-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Stairway+Series/72442/">Stairway to SQL Server Indexes: Step 10, Index Internal Structure</A>[/B]Mon, 28 Mar 2011 15:53:28 GMTDavid Durant