November 10, 2017 at 7:30 am
Hello, I took over a SQL Server 2016 system 1.5 yrs ago, and it connects to a Teradata DW for data source. From the beginning they setup the Teradata driver and Attunity provider both as as 32 bit. Since, I have installed the 64bit Teradata Driver and 64bit Attunity Provider. I attempted to make a new Connector, that the load steps would use, but it still running at 32 bit. I also went into the Job step props and was able to flip the off the 32bit runtime and it runs with no errors. What do I have to do to get an SSIS Pkg to use the 64 bit Teradata and Attunity drivers and providers? I can see in the Pkg that does use the Teradata/Attunity driver/provider using TPT to fastload the SQL Server table, that it has: ForcedExecutionValueType, and it's set: Int32. Is it this simple, to change it to Int64, and then Build and Deploy?Thanks
November 10, 2017 at 7:39 am
quinn.jay - Friday, November 10, 2017 7:30 AMHello, I took over a SQL Server 2016 system 1.5 yrs ago, and it connects to a Teradata DW for data source. From the beginning they setup the Teradata driver and Attunity provider both as as 32 bit. Since, I have installed the 64bit Teradata Driver and 64bit Attunity Provider. I attempted to make a new Connector, that the load steps would use, but it still running at 32 bit. I also went into the Job step props and was able to flip the off the 32bit runtime and it runs with no errors. What do I have to do to get an SSIS Pkg to use the 64 bit Teradata and Attunity drivers and providers? I can see in the Pkg that does use the Teradata/Attunity driver/provider using TPT to fastload the SQL Server table, that it has: ForcedExecutionValueType, and it's set: Int32. Is it this simple, to change it to Int64, and then Build and Deploy?Thanks
ForcedExecutionValueType is not relevant.
Sounds like you did the right thing. How do you know that it used the 32-bit drivers?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
November 10, 2017 at 7:51 am
The slow bandwidth of throughput not changing , and looking at the dir paths, doesn't seem to point to the 64 bit, and I don't know how to make or force it to use all 64 bit Teradata driver and 64 bit Attunity provider.
November 10, 2017 at 8:26 am
quinn.jay - Friday, November 10, 2017 7:51 AMThe slow bandwidth of throughput not changing , and looking at the dir paths, doesn't seem to point to the 64 bit, and I don't know how to make or force it to use all 64 bit Teradata driver and 64 bit Attunity provider.
Can you elaborate on what 'dir paths' you are referring to?
It should use the 64-bit drivers as long as the 64-bit version of DTExec is being called.
And it will be called, as far as I know, if you have unchecked the 'Run 32-bit mode' check box in the relevant SQL Agent job step.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply