Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Bulk load data conversion error (truncation) for row 1 Expand / Collapse
Author
Message
Posted Thursday, June 18, 2009 10:32 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 3:28 AM
Points: 37, Visits: 251
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
Post #738043
Posted Friday, June 19, 2009 2:59 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, April 22, 2014 6:56 AM
Points: 1,330, Visits: 1,434
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
Post #738121
Posted Monday, June 29, 2009 2:04 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 3:28 AM
Points: 37, Visits: 251
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
Post #743405
Posted Monday, June 29, 2009 7:56 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, March 21, 2013 7:08 AM
Points: 55, Visits: 119
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.'
Post #743630
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse