Home Forums SQL Server 2016 SQL Server 2016 - Development and T-SQL When is too many columns too many columns? RE: When is too many columns too many columns?

  • January 16, 2018 at 7:20 am

    #1975980

    Grant Fritchey - Tuesday, January 16, 2018 6:13 AM

    If you really only need a flat file, use a flat file storage system or a document database, not an RDBMS.

    I'll say, "It Depends".  Such a thing is certainly better than storing large XML or JSON junk and may be entirely necessary because an RDBMS will still handle files (once imported into a table) better than a whole lot of other things especially if it is data such as CDRs or similar information.

    Yes, writing mediocre code runs faster than writing bad code. Well done. What if we actually write good code?                       

    +1000 to that!

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