Common SQL Server Mistakes

  • Comments posted to this topic are about the item Common SQL Server Mistakes

  • Steve, nice info for a beginners tract on a SQL Saturday. Now how to lure you to SQL SAT #60 (Cleveland)...

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • I'll try to make it. Not sure about the timing

  • Well, apparently sign me up, shame I'm nowhere near it.

    Anyone give me the short form as to why these two are included?

    IS NULL

    Multi-row triggers

    I wouldn't consider auditing an edge case for multi-row triggers, and I'd want to audit on the bulk change.

    IS NULL I use a lot, though that may have more to do with not being as familiar as I should with EXCEPT and/or MERGE and use it against left joins a tremendous amount. Unless this discussion is focusing on its usage under AND ( @blah = blah OR @blah IS NULL) in WHERE clauses.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • The presentation talks about people writing "=null" not "is null", and gives the latter as the proper way to test for NULL.

    Multi-row triggers are something that people commonly do not write as well. Too often I find people writing select @i = ID from inserted and not accounting for multiple rows.

  • Steve Jones - SSC Editor (10/20/2010)


    The presentation talks about people writing "=null" not "is null", and gives the latter as the proper way to test for NULL.

    Multi-row triggers are something that people commonly do not write as well. Too often I find people writing select @i = ID from inserted and not accounting for multiple rows.

    Ah-ha! Mistakes while using them, not the mistake is the use of. That makes a ton more sense. Thank you for the clarification.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Steve Jones - SSC Editor (10/20/2010)


    I'll try to make it. Not sure about the timing

    Thanks for considering it (us) ....

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply