Annoying thing about this is it worked just 2 days ago but has stopped working and for the life of me, I can't think why from the changes I've made.
I'm using Visual Studio 17, SQL Server 2016 and the ODBC Driver for Teradata 15.10.03 from Teradata.
What happens is, if I include any date or time columns in my Teradata input query, the package fails on the source component with VS_NEEDSNEWMETADATA. I've tried building a new package with just a Teradata source component in it with the query fetching just one of the dates and that comes up with the same error so advice I saw that suggested removing and recreating the input component didn't help.
Interestingly when I view the External column definitions for the dates and times they all show as Byte Streams. I can't say whether that was the case when it last worked as I hadn't looked.
I also tried changing the query to cast the dates and times as strings and that changed the external definition to string but the same error still happened.
Just to prove it wasn't the query in general, I removed those 3 columns and all worked fine.
I thought it might be that our technology people have updated the ODBC driver but I get the same error when running in Visual Studio on my desktop and I know that hasn't been updated.
I don't have any control over the Teradata source but the view I'm applying my query to has been created specifically for my team so I can always ask the developers to change the definition of those columns to cast as string which I can then convert back once I've input it but that seems a cop-out.
Has anyone else ever experienced anything similar? If so, did you find a solution?
This is the definition of my cut down source component. If I click preview, I get data.
And this shows how SSIS interprets that column in the Advanced Editor
Finally the error when I run it:
I've tried running this against both Production and OAT instances of Teradata in 2 different domains but it makes no difference.
Nick Ryan MIS Programmer Analyst, ANZ Bank