Is there a workaround for this issue that doesn’t require me to tell my application developers they have to change all their code? Something I could do at the index level? Thanks.

Yes, that works too! I’ll edit my post with your suggestion too. Thank you.

Michelle

I actually mispoke (mistyped?) a little. I thought the error message was returned that way because it was called via stored proc, but really you would get the same error message if you just try to force the hint in an ad-hoc query, too.

You receive the error message because Query Optimizer, sometimes correctly and sometimes incorrectly, perceives that it will be unable to fulfill the request using the index you specify. The only case I’ve ever seen this in (so far) has been a filtered index. Hopefully that helps, and good luck!

Michelle

I think that if you explicitly tell the optimizer that your parameter fits into the filter. Instead of:

SELECT DISTINCT myData
FROM dbo.filteredIndexTest
WHERE myDate >= @myDate1;

let us try this:

SELECT DISTINCT myData
FROM dbo.filteredIndexTest
WHERE myDate >= @myDate1
AND myDate>’theThresholdInMyFilteredIndex’

What do you think, Michelle?

However, I am much more interested in what causes this error in the first place. You state, “…since this was a stored procedure, I was receiving the following error message…” implying this is due to sprocs. However, we’ve been using index hints in sprocs for years, and have never received this error. I am curious why I am getting it now all of a sudden on one specific sproc. Do you or any of your readers have insight on that?

Thanks!