Home Forums SQL Server 2014 Administration - SQL Server 2014 export table RE: export table

  • September 3, 2014 at 10:00 pm

    #1743070

    Eirikur Eiriksson (8/25/2014)

    Jeff Moden (8/25/2014)

    Eirikur Eiriksson (8/25/2014)

    Feel I'm starting to repeat my self on the issue:pinch:

    BWAAA-HAAA!!! Me too!

    Switching from one delimiter to another is a form of procrastination, not a solution.

    I'll have to register my strong disagreement with that statement. 😉 For example, TSV is so much easier to implement that switching the delimiter to TABS IS one of the better solutions. The CSV standard that you've cited is fraught with vertical (inconsistent) exceptions that cause a world of hurt for those that have to import it. TSV solves most of those problems, especially in the world of BULK INSERT, quickly and easily.

    Until a field/record/column contains TAB characters then oops lets switch to PIPE....;-)

    😎

    True enough... that's when then sometimes find out that they have both TABs and PIPEs in their data. It would be a lot simpler if we went back 40 years and used the correct ASCII characters for text data transmissions... characters 28 through 31 in the ASCII table.

    http://www.asciitable.com/

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