Jul 26, 2018 11:59 AM|PatriceSc|LINK
Depends on how you access those rows most often. For example if you always use an A, B criteria it could be better to keep index2 and drop index1.
Ah, in most db you should be able to check index statistics to see how they are used before dropping them. You are using SQL Server ?
Edsit: for example something like https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-db-index-usage-stats-transact-sql?view=sql-server-2017 should
help to take an informed decision,
(still add your own knownledge, for example an index could be really useful for a rare operation)