June 16, 2011 at 3:59 am
Hi!
I have an index a SQL server 2005 standard edition database the I would ideally like to drop as it has appeared on my proactive index usage sweep for over a year as having 0 accesses, 0 scans and 0 lookups. Thing is it is on the biggest table in the database interms of row number and size. Total table size on disk is 100Gb with 1.4 billion rows. I would like to have as little an impact on the database as possible. I was considering disabling the index before dropping. Has anyone had any experience on doing this type of thing on such a large table and what kind of inpact did it have?
Kind Regards
M
June 16, 2011 at 4:33 am
If you're going to drop it, then drop it. Disabling an index removes the b-tree and leaves the metadata. Dropping it removes the b-tree and removes the metadata.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply