February 24, 2017 at 4:12 pm
I'm not really sure where to ask this question, if this needs to be relocated my apologies.
Platform: Windows 2012 R2 Standard, with SQL Server 2016 SP1 EE, Visual Studio 2015 Community w/ SSDT4 and Attunity for Teradata, Existing system has several SSIS and SSAS Tabular cubes; Data warehouse: Teradata 15.10.02.11
Recently went through finding why connection and data transfer at 32 bit. Job flag for connection SS and TD must be set 32bit or fails.
Though using Teradata 64bit driver on SQL Server, installed Attunity for Teradata Connector 64 bit, created new connector in VS using Attunity 64 bit connector in packages, build and deploy..., when the job runs, if you change Job flag to 64 bit, it fails, must only run with 32 bit flag on.
The error I get from SQL Server, the first error of the many: "The Teradata TPT Registry Key can not be opened, verify the TPT API 12 or 13 for Windows x64 is installed properly." Leads me believing the TTU are not installed, as I can't exactly find them, though I can see where an install of Teradata items were installed, much typical client side stuff mot TTU's.
My question, did you install Teradata Utils like TTU for Windows 64 bit on your machine, so your connections for Jobs run as 64 bit, and you still create the Attunity connector as usual from Visual Studio? How are you able to accomplish 64 data transfer through the ODBC drivers between SQL Server and Attuinty to your Teradata platform?
Thanks,
JPQ
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply