KBSK (11/2/2016)
Grant Fritchey (11/2/2016)
Just curious, what about the right hand side? You can write a query that puts a function against a column on either side of the operand and it will behave exactly in the same way (depending on the operand, of course).In where clause, I am assuming the left hand side operand are Table columns and right hand operands are search arguments. (Hopefully)
The purpose is to identify these scenarios and mofify the queries to make use of index.
Thanks,
Santhosh
Don't waste your time.
With this approach you'll be digging through heaps of false positives and miss the real ones.
Did you think about views/derived tables/CTE's using DISTINCT keyword?
What about pivoted tables joined to some other tables?
You don't always need a function in WHERE clause to screw things up.
Better find queries with "fat" execution plans (Jeff pointed you into the right direction) and try to find out what is causing those "fat lines" on the execution plans.
_____________
Code for TallyGenerator