• Nah... you're not jaded... experienced and wise is more like it. I've see the same ridiculous things, even recently, like having the front end create and transmit a quarter million very wide, full up, INSERT/VALUES statements instead of (in this case) passing 8 parameters and letting SQL Server generate the quarter million rows as a single insert would work so much better at all angles. Then, to add insult to injury, they had the nads to blame the database for it taking so long and the customer's network for not being able to get anything else done when a couple/three of these things ran at the same time.

    And I don't think you're anti-dynamic-SQL. You're just like a lot of the rest of us that are long in tooth... we normally say "It Depends" but we get our hackles up when we see stuff that we have already seen go south in the past because of a not so rare combination of ignorance, stupidity, and the "I just want to get if off my plate" attitude. We also don't want to read about ourselves in the news as being the latest company that got hacked due to SQL Injection.

    --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)