if anyone has a suggestion on dropping any other index that will be great.
Supposedly, you know more about that table than we do. It's difficult to suggest about indexing on a table I know nothing about.
Another question is if i ve one index on column1 and another one on column 1 and column 2 then can i drop first index thats solely on column1 as this column is covered by 2nd index.
Probably. However, say that this query is very important:
SELECT column1, COUNT(*) FROM tbl GROUP BY column1
If you drop the index on only column1, this query will run slower, as it now has to scan the composite index on (column1, column2).
But, yes, in most cases you can consider such indexes redundant. I think I noticed a few more in the list above.
how can i check the impact of dropping these indexes other than testing in lower environments.
You drop them in production, and then waits to see if someone starts screaming.
More seriously, you can dig in the plan cache to see which queries where these indexes are used, but I don't have any query canned for that. And I am not sure that it's worth the effort.