Recently we uncovered a long running proc and one of my colleagues pointed out that that dropping the ISNULL in the where clause sped things up for reasons pointed out in this post Is there is any Performance issue while using ISNULL() in SQL Server?. I did some Google searching but couldn't find out for sure if there was any danger in missing data. I know if you say something like this
WHERE ID NOT IN (SELECT MemberID FROM Person WHERE MemberId IS NOT Null)
and MemberId is nullable you won't get any matches if you don't include the "IS NOT NULL" but I think that is a different issue? Maybe not?
Here is the change my coworker is proposing.
where ISNULL(ct.DisabilityBenefitsConnectAuthorized,0) = 1
Would become
where ct.DisabilityBenefitsConnectAuthorized = 1
It doesn't seem to be effecting results however I am not 100% sure that it couldn't and we just don't know it.