• Sean Lange (11/24/2014)


    paul s-306273 (11/24/2014)


    Reading 'XYZ', I'm surprised that the use of views is discoraged.

    You read that document (which btw is more than 6 years old) and you were surprised about the use of views being discouraged?

    How about some of the other interesting things in there (no offense meant Jeff):

    All the object prefixes sounds like a blast from the past. I would be surprised if that were something you would put together today as object prefixes tend to make things more difficult.

    How about this one?

    1.All tables (except temp tables and table variables) and views that are not the target object of an Update, Insert, or Delete statement, must be accompanied by the WITH (NOLOCK) optimizer hint. The use of (NOLOCK) without a WITH is discouraged.

    That does not sound like something that Jeff would put his name on today.

    All in all it is a great example of how to put this together but I would be careful about just grabbing that document today and using in any environment.

    That last one was because that was a standard heaped on me by an employer. I didn't know enough about it back then to know how bad that little suggestion actually was.

    The point that I believe that you're trying to make is a great one. Understanding changes faster than the actual code and what was right yesterday might not be today... and I whole heartedly agree.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)