Warning: Index ‘IX_NonClustered_TableName’ on table ‘TableName’ was disabled as a result of disabling the clustered index on the table.

So if you disable the clustered index it automatically disables the non-clustered index, but if you rebuild the clustered index the non-clustered doesn’t get automatically rebuilt. Is that what you are getting at?

A good article on SQL Server Indexes to clear all the doubts. Appreciate it!

There is a little typo in the last paragraph. I have read it, and read it again to convince that there is not, but could not help myself much.

The last para says “From the example, it is very clear that if you have *built* only clustered index when the nonclustered index is disabled, it still remains disabled. Do let me know if the idea is clear. ”

which confused me *a bit* initially until I read the whole write-up again.

It should have been “From the example, it is very clear that if you have *rebuilt* only clustered index when the nonclustered index is disabled, it still remains disabled. Do let me know if the idea is clear. ”

May be you already have had received same response from your readers, I am perhaps not aware, didnt check all the replies for this!

Just thought to bring it to your kind notice, to make your write-up more robust.

Thanks & Regards!
Sumit M.

Thanks for the explanation.As I understand Rebuilding an index will drop the index and will re-create the same which is causing this behavior.

Thank You,
Anup