It really is going to come down to how many nonclustered indexes you have on the table, how many transactions per second are writing to the table and how the SQL Server's storage is configured.

Which raises the question: Why is SQL Server ignoring the index? If your table has a lot of rows and SQL Server is ignoring your index, typically the reason is that your index isn't subdividing the ...