• David.Poole - Monday, June 4, 2018 2:19 AM

    Those man weeks we had spent coding, testing and integrating could have been achieved in hours if we had known more about the CMS features.  There was also an aspect of trusting the CMS framework. 

    This is why I say that little play on words of "Just because you can do something in SQL, doesn't meant you shouldn't".  SQL Server is a remarkable tool that a lot of people try to avoid from the front end or brute force things with PowerShell, etc, and then wonder why their code is slow and difficult to maintain.

    In the SQL Server world there is inappropriately writing SQL in a way to force an execution plan thus blocking any benefits that come with upgrades to the query engine


    Worse than that, I find that a lot of people write SQL that blocks any benefits that come with the product as it currently is.

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