• Thanks everybody!

    I actually saw the IF construct in several stored procedures that I was asked to review, and it made me wonder why somebody would do that. Cause, I'd probably just do the JOIN construct, and not even think to use the IF. I guess it stuck out to me 'cause it had a kind of funky smell. 🙂

    Anyway I'm going to suggest that we (the company I work for) change the IF construct to the JOIN construct. The .NET code is already checking for a null dataset, null table and empty rows collection. So, it shouldn't hurt anything on the .NET side. It'll just be making checks it doesn't need to anymore.

    Thanks,
    MKE Data Guy