or
mikaelnet imported from SE
sql-server sql-server-2017
I have a quite large table (>10M rows) with frequent crud operations. It has proper indexes, but they get fragmented quickly. Without a periodic index reorganize/rebuild maintenance plan, the index fragmentation can easily go over 90%. 

Right now I've addressed this by reorganizing the indexes on a daily basis and a rebuild on a weekly basis. I've also played around with fill factors etc to keep the fragmentation lower.

My main problem is that when the indexes gets too fragmented, SQL Server ignores the indexes and performs full table scans instead. When that happens, it almost kills the application since repeatedly scans of such large table is really heavy. I'm quite sure using a fragmented index would be faster in those cases.

Is there a way to let SQL Server use the index regardless of its fragmentation? 
Top Answer
Erik Darling
Index Hint
--
You can use an [index hint][1] to do that:

    SELECT *
    FROM dbo.Users AS u WITH (INDEX = ix_definitely_an_index)
    WHERE u.Reputation = 2;

The downsides are:

 - Potentially changing a lot of code
 - If you rename an index, this breaks
 - If you change an index definition, it might not be the best index to use anymore

Plan Guides
--
You can also use a [Plan Guide][2], which sets the plan you want in place.

The downsides are:

 - It's fickle; if your query isn't exactly the same, your plan might not get used
 - It's tough to set up; you have to get everything exactly right
 - Also the same stuff as an index hint, so uh... That's rough.

Query Store?
--
Since you're on SQL Server 2017, you may be able to use [Query Store to force plans][3]. This is much easier than using a Plan Guide, but you may end up with an [unexpected plan][4].

Downsides:

 - Same stuff as above
 - Having to enable Query Store, if you're not already using it
 - Having to query Query Store to see if forced plans are failing

Alternatives
--
Without knowing more, I'd probably be more keen on investigating if the index use changes for other reasons, like [parameter sniffing][5].


  [1]: https://docs.microsoft.com/en-us/sql/t-sql/queries/hints-transact-sql-query?view=sql-server-2017
  [2]: https://docs.microsoft.com/en-us/sql/relational-databases/performance/plan-guides?view=sql-server-2017
  [3]: https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-query-store-force-plan-transact-sql?view=sql-server-2017
  [4]: https://sqlworkbooks.com/2018/03/what-is-a-morally-equivalent-execution-plan-and-why-is-it-good/
  [5]: https://dba.stackexchange.com/q/204565/32281
Force SQL Server to use fragmented indexes?

This is a dedicated room for discussion about this question.

Once logged in you can direct comments to the question poster (or any answer poster) here.