Hi,I've come across a peculiar case in the database I'm administrating. Have a look at this:EXEC sp_help 'base_customers'--> Results:index_name index_description index_keys_dta_index_BASE_CUSTOMERS_7_1615500984__K1_5 nonclustered, hypothetical located on PRIMARY Customer_No_dta_index_BASE_CUSTOMERS_7_1615500984__K1_K5 nonclustered, hypothetical located on PRIMARY Customer_No, Customer_type_id_dta_index_BASE_CUSTOMERS_7_1615500984__K5 nonclustered, hypothetical located on PRIMARY Customer_type_id_dta_index_BASE_CUSTOMERS_7_1615500984__K5_K1 nonclustered, hypothetical located on PRIMARY Customer_type_id, Customer_No_dta_index_BASE_CUSTOMERS_c_7_1615500984__K1_K5 nonclustered, hypothetical located on PRIMARY Customer_No, Customer_type_idIX_CUSTOMERS_NAME nonclustered located on Common Customer_NamePK_BASE_CUSTOMERS nonclustered, unique, primary key located on Common Customer_No
Now I've read that hypothetical indexes are created by the Index Tuning Wizard but SQL Server Management Studio lists them under Statistics for this given table and not under Indexes which I would expect. So I'm a little confused...are they indexes or statistics? I have tried to run "drop index [BASE_CUSTOMERS].[_dta_index_BASE_CUSTOMERS_7_1615500984__K1_5]" but it takes forever and causes deadlocks to happen in the database...shouldn't dropping a nonclustered index happen instantly?--Henning