too many indexes

Question

Hi All,

Recently we are having issues with disk space requirements.

After monitoring db file growth for a week,we found the index file is growing rapidly (100gb-500gb). Other data files and log file space usage is stable. So, we wanted to clean up some of the unused indexes. So, what is the criteria.

Based on my knowledge, we can disable those indexes which have low reads vs high writes. I need more suggestions on how to go about cleaning up some of those unused indexes. I use below glenn berry DMV little modified to find out unused indexes.

Attaching the excel sheet which contains index usage stats data. please suggest some solutions. Since i am unable to attach .zip file , i renamed the file as .txt. once u have download the file, please rename "index info.txt" to "index info.zip".

Note: Application team has ddl_admin permissions to create objects. As per vendor database specifications, they need those permissions.

Questions :

1. Can we straight away disable those indexes whose reads = 0 but writes are high ?
2. When to disable when to drop those unused indexes?
3. Our index maintenance jobs runs over the weekend. When to disable or drop to have clean stats? by Friday?
4. Do we need to collect more data before disabling or dropping?
5. Some of the indexes have 0 Rowcount but i can see writes in that indexes , reads = 0 , so what does it mean? PFA screenshot

Regards,

Sam