Re: Data conversion failed while converting column "officename" (70) to column "officename" (250).
- From: Allan Mitchell <allan@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Dec 2006 22:59:44 +0000 (UTC)
Hello IanO,
So you should be setting the OnError for the columns in the Source Adapter to Redirect the rows down the Error Flow. As Todd has said you can almost debug this before you try to load by using a Row Count transform
BTW use Our's it's cooler.
http://www.sqlis.com/default.aspx?77
Send your rows to a No-Op destination like the trash destination
http://www.sqlis.com/default.aspx?56
In an expression then on the workflow after the Data Flow task decide what you want to do. You could take a view that if the ratio of Good:Bad is less than a given %ge then do not carry on.
Regards
Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com
Please tell me how I can GLOBALY change the default error handling to
just keep going.
It is far more important that I get the good rows then stop on one bad
one.
This error is reported from the Data Flow Control Flat File Source.
For some time, I have been changing fail on error to ignore anywhere I
can find it.
Sometimes, it seems that SSIS is changing it back.
I'm hoping that you know of some config option that will let me make
this change.
In the meantime.. what could possibly be wrong with an office name to
cause this failure?
Thanks,
IanO
.
- Follow-Ups:
- References:
- Prev by Date: Re: SSIS: ET flat text file to multi-level hierachal XML.
- Next by Date: Re: importing space delimited text file
- Previous by thread: Re: Data conversion failed while converting column "officename" (70) t
- Next by thread: Re: Data conversion failed while converting column "officename" (70) to column "officename" (250).
- Index(es):
Relevant Pages
|