• Steve Jones - SSC Editor (7/6/2015)


    ...the problem is MS is not investing in the tooling or features beyond what's needed to get a sale. That's short term thinking that allows other tools and platforms to gain traction.

    You took the words right out of my mouth. If they spent just one version fixing or bringing up to date those things that need it (and that includes a lot of "Closed - Working As Designed" items) and things like fixing ACE drivers and updating BCP and fixing things like the privs problems associate with BULK INSERT and whole lot of other things with the engine and TQL itself (seriously!!! Like the fact that shrink still doesn't work correctly, etc), then a whole lot more people would have a whole lot better opinion of both MS and SQL Server.

    And, while it's understood that Azure is important to future success, fix the product/customer base that you already have in the stand-alone product and then migrate those fixes to Azure. It's a win-Win-WIN for anyone and everyone involved.

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