Post reply

Import 1.2 gig tab-delimited file into SQL Server 2005

  • January 14, 2011 at 9:23 am

    #233288

    Hello Everyone,

    The CR and \t characters are messing up 2 columns. I believe they are interpreted literally. I cannot fix this at the data entry point through validation. Extra columns are produced on the next line.

    I'm thinking, either

    a) a workaround to redirect these error rows into a destination source and then apply another (T-SQL) processing algorithm to it and insert the row into the original destination table or,

    b) strip the CR and \t characters first from the tsv, then load.

    Any ideas would be greatly appreciated!

    Thanks all--

  • January 14, 2011 at 2:58 pm

    #1273820

    colladay (1/14/2011)

    Hello Everyone,

    The CR and \t characters are messing up 2 columns. I believe they are interpreted literally. I cannot fix this at the data entry point through validation. Extra columns are produced on the next line.

    I'm thinking, either

    a) a workaround to redirect these error rows into a destination source and then apply another (T-SQL) processing algorithm to it and insert the row into the original destination table or,

    b) strip the CR and \t characters first from the tsv, then load.

    Any ideas would be greatly appreciated!

    Thanks all--

    Can you post a sample row what your input data looks like? If you have these special symbols in your columns, they should be quoted (").

    ---
    SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply