I have a table where the Clustered Index is unique and made up of 5 fields as follows:
ProductID int, ProductSCDID int, StartDateID int, StoreID smallint, SellingPriceTypeCode int
In a table with 550 million rows, this is quite a large clustered index.
Would it be more efficient for storage and index creation if I created a computed column which creates a unique hash value of all these keys, and make that the unique clustered index?
The queries make better use of the non-clustered indexes than they do this clustered index, so I'm not concerned about how useful it is for querying.
Also, the table is truncated daily and re-loaded from a warehouse so the clustered index is dropped and re-created every time. I'm trying to make the creation of the clustered index as fast as possible.
I'm having the debate about whether the table needs a clustered index at all seperately. This is just to decide whether there's any benefit in investigating this as a possible solution. Has anyone tried it before?