This should be fixed. Last week, we made changes to the query to adjust a couple of indexes and 'hey, it worked', but then we did the maintenance yesterday which failed the database over to a different server and guess what it decided to stop working as expected.

All of the indexes were the same, but the SQL Engine picked a different execution plan for the page which was not the plan we wanted. The good news is that last week, I turned on query store for SQL Server which captures different execution plans for queries. The query store captured both the good and the bad plan, and one of the nice this about this is it let's me tell the server to use the good plan. I just forced the plan for the query and it should be loading now.

This should be fixed. Last week, we made changes to the query to adjust a couple of indexes and 'hey, it worked', but then we did the maintenance yesterday which failed the database over to a different server and guess what it decided to stop working as expected.

All of the indexes were the same, but the SQL Engine picked a different execution plan for the page which was not the plan we wanted. The good news is that last week, I turned on query store for SQL Server which captures different execution plans for queries. The query store captured both the good and the bad plan, and one of the nice things about this is it lets me tell the server to use the good plan. I just forced the plan for the query and it should be loading now.