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

SSIS Package fails in Production Expand / Collapse
Author
Message
Posted Thursday, January 3, 2013 7:00 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 30, 2013 9:31 AM
Points: 19, Visits: 228
I have created a SSIS data flow package in our development environment that works via debug or sql agent. but when I point the data source to our production database ( copy of Dev database) the package fails on the ADO NET destination.

The errors in the execution results:

[ADO NET Destination [213]] Error: An exception has occurred during data insertion, the message returned from the provider is: String or binary data would be truncated.

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "ADO NET Destination" (213) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (216). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.


[Flat File Source [1]] Error: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Flat File Source" (1) returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.

Post #1402346
Posted Thursday, January 3, 2013 7:07 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Monday, October 13, 2014 6:42 AM
Points: 5,216, Visits: 5,111
String or binary data would be truncated.


You have data going into a column which it cannot fully store.

Eg Trying to insert VARCHAR(100) into VARCHAR(50)

Debug the source columns and ensure that the destination columns match the correct data types and lengths.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1402355
Posted Thursday, January 3, 2013 7:40 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 30, 2013 9:31 AM
Points: 19, Visits: 228
Thanks for the quick response.

What I find interesting is that the package works fine when I point to Development which was used to restore the production database.
Post #1402384
Posted Thursday, January 3, 2013 8:41 AM


Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Friday, October 10, 2014 1:07 AM
Points: 692, Visits: 2,803
Debug the source columns and ensure that the destination columns match the correct data types and lengths.


+1

What I find interesting is that the package works fine when I point to Development which was used to restore the production database.


Sounds like one has been changed...

Andy


==========================================================================================================================
A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila. Mitch Ratcliffe
Post #1402416
Posted Thursday, January 3, 2013 11:41 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 30, 2013 9:31 AM
Points: 19, Visits: 228
Solution:

The Flat File Connection Manager had the Text qualifier as _x0022_. When I changed it to " (double quotes) on the production SSIS package it works as advertised.

Thanks for the Quick Replies and Happy New Year!!
Post #1402489
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse