Post reply

Bulk load data conversion error (truncation) for row 1

  • June 18, 2009 at 10:32 pm

    #73721

    Hi,

    I am getting the following error while doing a BULK Insert.

    column 1 (a).,Bulk load data conversion error (truncation) for row 1, column 1 (a).,Bulk load data conversion error (truncation) for row 1, column 1 (a).,Bulk load data conversion error (truncation) for row 5, column 1 (a).,Bulk load data conversion error (truncation) for row 1, column 1 (a).,Bulk load data conversion error (truncation) for row 2, column 1 (a).,Bulk load data conversion error (truncation) for row 6, column 1 (a).,Bulk load data conversion error (truncation) for row 2, column 1 (a).,Bulk load data conversion error (truncation) for row 5, column 1 (a).,Bulk load data conversion error (truncation) for row 3, column 1 (a).,Bulk load data conversion error (truncation) for row 2, column 1 (a).,Bulk load data conversion error (truncation) for row 7, column 1 (a).,Bulk load data conversion error (truncation) for row 6,

    This bulk insert is done through a SP and is called by EXCEUTE SQL TASK in a SSIS package. Another point is that this error does not come on all the machines; though we have same SQL server edition and service pack on these machines.

    Any help/clue would be appreciated.

    Thanks

    PS

  • June 19, 2009 at 2:59 am

    #1012231

    Hello,

    Sorry for asking, but just to be sure, is the data in the first ”column” of the import file too wide to fit in the target table’s column?

    Regards,

    John Marsh

    www.sql.lu
    SQL Server Luxembourg User Group

  • June 29, 2009 at 2:04 am

    #1016643

    John,

    I checked the length of the field and column. They are in sync.Also when I re ran my package, it executed without any problem. I am looking for the reason why it happened. Will post it if I get any clue.

    Thanks

    Parul

  • June 29, 2009 at 7:56 am

    #1016832

    I'm guessing that today, you got some data in your upload file/source that is missing. I'd first start checking date fields for missing, null or incorrect syntax.

    Then move onto the numeric fields.

    I know one of the things I always did writing DTS/SSIS was put in checks on my date fields that if they were null, I defaulted to something like '1/1/1970.'

Viewing 4 posts - 1 through 3 (of 3 total)

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