title: Clustered versus nonclustered index in a SQL Server table
body: <p>Working in a datawarehouse environment (SQL Server 2008) and there are a few tables that have about 2 million rows and 20 columns. Each night, the tables are dropped and re-created. When they are made, indexes are also built. For some reason there is no clustered index on these tables. There are however, unique nonclustered indexes. Seems unlogical. Does anybody know any downsides to changing that all so that all these tables have a clustered index. Should save some space and perform better.</p>
  
  <p>Any tips?</p>
  
  <p>Thanks in advance.</p>