mtassin (8/7/2012)
MyDoggieJessie (8/7/2012)
All jokes aside 😉 when removing the index hint the optimizer automatically turns it into an index scan...so that's why I was trying to force it to use the index I had created specifically for it.
That's not always a bad thing... an Index Seek that involves Bookmark/RID lookups is generally worse than an index scan that doesn't.
Just as one example.
This is kinda why I suggested he run a timing test with and without the INDEX hint.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St