November 3, 2011 at 4:01 pm
I'm confused about a ssis package we have an issue recently.
The package is basically to export from a flat file to a sql table.
It uses the data flow task, in the middle of the task it uses a script task to convert some date string to stored as integer. It ran OK until last week I add another varchar column at the end of the file.
Some date columns showing not correct data.
Then we cannot figure out why it is wrong, all the other columns look correct except the date columns data.
Then one of the developers tried to change the first date column name to another one, and then it seems sychronized all. and all the other date columns show correctly
It works since that, I'm kind of confused why change column name make the package work again.
Before that, I did do reset columns, but it didn't fix it.
November 3, 2011 at 4:45 pm
It sounds like the metadata just needed updated. By chance were the two columns similar in name? Or did you remove one, then add it back and then add the new column?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 3, 2011 at 5:03 pm
SQLRNNR (11/3/2011)
It sounds like the metadata just needed updated. By chance were the two columns similar in name? Or did you remove one, then add it back and then add the new column?
Thanks, what I added is a varchar column at end, it works fine.
But some date columns before that got messed up. There is a script task in the middle of the data flow that convert the date to string to integer.
When I first do this, I did go to data source file connection, and reset columns.
But it seems the part in the script task somehow is not synched, I just want to avoid this problem when later we add other columns.
But the way the developer fixed that by changing the first date column in the source file connection manager makes all this correct, not sure why?
Thanks
November 3, 2011 at 6:11 pm
Because it (what the developer did) resyncs the metadata. That is what has happened here.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 3, 2011 at 7:33 pm
Thanks, Yes, I undstand that,
But at first when I do that, I reset the columns of the flat data source, and it should resync the columns too, the point I don't understand is why we have to rename a column and then it resynchronize.
Thansk
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply