Microsoft Connector for Teradata for SQL Server 2019 is released

ArmandoContestabile "OData Source" is default component. Are you in the "Data Flow" tab in the design canvas? 

Hi, simee5

It is a limitation now that the error table can only be created in the user database. It does not recognize the [schema].[tablename] format. We will provide a fix for it.

Hello,

We are having the same issue as user (@simee5) regarding the Teradata error tables.

You mentioned a fix was coming for this issue - has that been released? If so, where can we update our drivers/tools to bring in this new change?

If not, is there an ETA on when the fix will be made available?

Thanks in advance!

Jordan

Hello Nandish732

I do not remember if this exact error i got but i know that i couldn't load to teradata into tables which had a column with "int" type. When i changed it to decimal it worked then. Just a hint. Try it in your case.

Regards.

Look at this article.

https://support.teradata.com/community?id=community_question&sys_id=9ff74fe31b97fb00682ca8233a4bcbe3

Hello, I'm looking for the extension that installs the "OData Source" component, like in your screenshots. I'm using Visual Studio 2019, and I've already installed SSIS extension. Thank you.

Getting this error when trying to copy data from "Teradata Source" to "OLE DB Destination" (MSSQL Server). Have adjusted  "JobMaxRowSize" and tried to change the "DiscardLargeRow" to both true and false. ANy suggestions? 

TITLE: Package Validation Error
------------------------------

Package Validation Error

------------------------------
ADDITIONAL INFORMATION:

Error at Data Flow Task [Teradata Source [16]]: The "Teradata Source" is missing the required property "JobMaxRowSize". The object is required to have the specified custom property.

Error at Data Flow Task [SSIS.Pipeline]: "Teradata Source" failed validation and returned validation status "VS_ISCORRUPT".

Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.

Error at Data Flow Task: There were errors during task validation.

(Microsoft.DataTransformationServices.VsIntegration)

------------------------------
BUTTONS:

OK
------------------------------

===================================

Error at Data Flow Task [Teradata Source [16]]: The "Teradata Source" is missing the required property "JobMaxRowSize". The object is required to have the specified custom property.

Error at Data Flow Task [SSIS.Pipeline]: "Teradata Source" failed validation and returned validation status "VS_ISCORRUPT".

Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.

Error at Data Flow Task: There were errors during task validation.

(Microsoft.DataTransformationServices.VsIntegration)

------------------------------
Program Location:

at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)

Kahlejj, we have identified an issue occurs when you design a package containing Teradata components in SSDT and set the TargetServerVersion lower than SQL2019. In that scenario, if you try to execute the package in SSDT, you will get the valiation error about missing properties like what you described. 

Is that your case?

We are working on the fix and it will be ready soon.

Temporary workaround for it: Instead of directly execute the package, close and reopen the package in the SSDT and then execute it.

Junxiao_Ma - Is this connector tested? For some reason this doesn't work for us. Whenever I drag and drop the Teradata source, I get the following error. Can you please help with this

Hi bharathsql86 - seems it indicates that the bits are registered but are somewhat located in the wrong location. Please try to uninstall and then reinstalled the Teradata Connector. Please also make sure you have installed Teradata tools and utilities.