SQL Server mainly maintains two structures for tables: Heap and Clustered. If there is no clustered index created with the table, table is with Heap Structure else it will be with Clustered structure.
Once the Clustered Index is created, SQL Server organizes data in a form of B-Tree and data pages related to the table will be held with the last level which is called as Leaf Level. Since the Clustered Index uses data pages, it is not possible to have another Clustered Index in the same table. Now the question is;
What will happen when the Clustered Index is dropped?
Many think that it is not possible because it holds data pages related to the table. But it is possible. If you drop the index, it goes back to the Heap and table will be maintained in the Heap. Here is a code that shows it;
-- creating a test table CREATE TABLE dbo.TestTable ( TestTableId int index ix_TestTable_Id clustered , TestTableValue1 varchar(100) not null , TestTableValue2 char(5) not null index ix_TestTable_Value2 nonclustered ); GO -- Inserting test records INSERT INTO dbo.TestTable VALUES (1, 'Hello world', 'ABC01') , (2, 'Hi', 'ABC02') -- Checks indexes availeble SELECT * FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('dbo.TestTable'), NULL, NULL, 'DETAILED');
-- Dropping the clustered index DROP INDEX ix_TestTable_Id ON dbo.TestTable; -- Checking the indexes and data after dropping SELECT * FROM sys.dm_db_index_physical_stats(DB_ID(), OBJECT_ID('dbo.TestTable'), NULL, NULL, 'DETAILED'); SELECT * FROM dbo.TestTable;