I’m working with very large data sets and I accidentally clicked on the “Fragmentation” tab on the properties page for the clustered index of a table. Management Studio did not handle this very gracefully. Everything locked up and Management Studio becomes un-usable.
What Managment Studio is doing is issuing a DBCC on the index to see what the fragmentation stats are. What makes this bad is that this table has 100,000,000 rows in it. Needless to say, this takes a while to complete.
I decided that I wasn’t willing to wait for the DBCC to finish so I used a KILL statement to end the process. Everything came back to life and I was able to dismiss the index properties dialog.
I wonder if it would be nice for SQL Server to have some idea if the DBCC will take a while and if it will, maybe it can be treaded off so that it doesn’t hang SSMS. Just a thought.