InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 06:28:53 GMT20http://www.sqlservercentral.com/Forums/Topic1419353-1550-1.aspx[quote][b]anthony.green (2/13/2013)[/b][hr]Yes I would aggree as the clustered index IS your table.[/quote]Great Stuff - Thanks for your inputWed, 13 Feb 2013 02:42:06 GMTSQLSACThttp://www.sqlservercentral.com/Forums/Topic1419353-1550-1.aspxYes I would aggree as the clustered index IS your table.Wed, 13 Feb 2013 02:39:24 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1419353-1550-1.aspx[quote][b]anthony.green (2/13/2013)[/b][hr]It needs somewhere to store the B-Tree so you would expect it to be slighltly larger after changing from a heap to a clustered index.[/quote]Thanks AnthonyWould you agree that a Clustered Index is absolutely NOT a seperate structure from your table?ThanksWed, 13 Feb 2013 02:37:01 GMTSQLSACThttp://www.sqlservercentral.com/Forums/Topic1419353-1550-1.aspxIt needs somewhere to store the B-Tree so you would expect it to be slighltly larger after changing from a heap to a clustered index.Wed, 13 Feb 2013 02:29:57 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1419353-1550-1.aspxHi AllI understand that when you create a clustered index, SQL Server doesn't create a physical structure seperate from the table. Initially I though that this can't be right because SQL allows you to create a table in one filegroup and then create the Clustered index in a different filegroup. I tested this and saw that when you create a Clustered index on a table in a different filegroup, SQL moves the table to the filegroup that contains the clustered index.My question> Why is it that after creating a clustered index, the size of the table increases slightly? Is this perhaps the pages in the non-leaf levels of the B-Tree?ThanksWed, 13 Feb 2013 02:25:04 GMTSQLSACT