July 20, 2010 at 3:34 am
Hi,
Once you change your column length or data type which you already defined in your source or destination we will get this error. To fix this try the following.
1. Go to source\destination editor
2. Then go to Columns tab (you can see columns tab at left side in editor)
3. Deselect the columns which you have modified and select in them again in the columns list
Hope this will works. It worked for me.
Seshadri A.V
February 22, 2012 at 5:06 am
I've come across the same situation.
The problem that we had was that we where using temp tables.
This normally isn't a problemen but SSIS packages don't alway retrieve the coloms that are passed through.
We solved this bij defining a table variable instead of a temp table and the SSIS package recognized the coloms.
Found the solution here: Source[/url]
Hope this helps.
June 5, 2012 at 1:49 pm
seshu.vnkt (7/20/2010)
Hi,Once you change your column length or data type which you already defined in your source or destination we will get this error. To fix this try the following.
1. Go to source\destination editor
2. Then go to Columns tab (you can see columns tab at left side in editor)
3. Deselect the columns which you have modified and select in them again in the columns list
Hope this will works. It worked for me.
Seshadri A.V
Wow, I can't believe I spend 3 hours trying to figure this out, this works for me 🙂
December 15, 2014 at 2:54 pm
I tried using the advanced editor to change the output size, which worked fine to change the "Output Column" Property. The issue for me was the "ODBC Source Error Output" column would not pick up that change and the GUI prevents the change to the correct size. This must be a bug in SSIS, because it should pick up the change or let you change it to the correct size through the GUI in the "ODBC Source Error Output". GAURAV UPADHYAY's suggestion to modify the XML worked for me. Just make sure you understand the XML enough to know where to modify the size, it is pretty straightforward with a CTRL + F on the column name.
December 16, 2014 at 1:57 am
Vernon Jimmerson-306463 (7/20/2010)
(using a friendly positive tone with a little smart *** worked in!)Or if they've had to deal with it for 15 years! There a thing called T-SQL code and BCP. You can script it, you can search for things in it. It's just SQL statements for the most part. If you want some special processing you can always write a CLR or two. You can script the CLRs also and look though the code easily. No graphical interface that you have to click on to figure you what the heck is going on! Code doesn't take an act of god to figure you how the data is being transformed or why the last guy wrote it with a loop control and a control for every data element being transformed or why he doesn't understand what row duplication is or unique record constraints.
If you can't script it into some readable code that can be searched like text than I don't like it.
That being said SSIS might be useful occasionally (wizard) but for the most part T-SQL, CLRs and BCP do fine and can be written in an object oriented way.
I'm glad we use SSIS then - your CLRs and BCP sound like a nightmare. SSIS is just so easy - and yes I've been using it since it was DTS and even that was OK but SSIS is sooo much better.
December 17, 2014 at 12:07 pm
I find in these situation I save a lot of time by dropping the source and creating a new one. If I had SQL coded I copy it ahead of time so as to just paste into the new source component. I can do that almost as fast as going in and trying to tinker with settings.
I also dont like to have SSIS reconfigure invalid colum references automatically. I double click the destination , go in delete all the old ones and select the mappings tab and it will usually reset them on its own.
----------------------------------------------------
January 5, 2017 at 10:40 am
Hi All,
Thanks for the help. I spent about 6 hours last night fighting with SSIS trying to get it to recognize a field length change. I ended up going with grasshopper's suggestion of editing the touchpoints in the XML, which worked out fine.
January 6, 2017 at 7:45 am
SSIS is a maintenance nightmare! Avoid SSIS like the plague. It's for people who shouldn't be coding at all! About the only exception I can think of is if you already have code and need to wrap it in SSIS so you can control bandwidth without having to process data in chunks!
I don't disagree with your implied comment that SSIS can be difficult to learn and you occasionally run into issues because it requires such a strictness with the data.
That said, I completely disagree with your conclusion to avoid it like the plague. SSIS is leap years ahead of DTS (though admittedly hard to see that at first) and when you have to do serious ETL coding will not cut it.
As for the original posts, I've never had trouble editing column width changes in the advanced editor. I'm surprised that it took making the alteration in the XML.
January 6, 2017 at 8:03 am
RonKyle (1/6/2017)
SSIS is a maintenance nightmare! Avoid SSIS like the plague. It's for people who shouldn't be coding at all! About the only exception I can think of is if you already have code and need to wrap it in SSIS so you can control bandwidth without having to process data in chunks!
I don't disagree with your implied comment that SSIS can be difficult to learn and you occasionally run into issues because it requires such a strictness with the data.
That said, I completely disagree with your conclusion to avoid it like the plague. SSIS is leap years ahead of DTS (though admittedly hard to see that at first) and when you have to do serious ETL coding will not cut it.
As for the original posts, I've never had trouble editing column width changes in the advanced editor. I'm surprised that it took making the alteration in the XML.
I agree.
Unless your data source is Excel, which will almost certainly result in anger-management issues! :w00t:
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 9 posts - 16 through 23 (of 23 total)
You must be logged in to reply to this topic. Login to reply