frederico_fonseca - Thursday, July 12, 2018 7:43 AM

Phil Parkin - Thursday, July 12, 2018 5:48 AM

quinn.jay - Wednesday, July 11, 2018 4:41 PM

frederico_fonseca - Wednesday, July 11, 2018 4:00 PM

32/64 bit has nothing to do with network speed - if speed is lower the issue is with the package and what it is doing and the configuration of the dataflow tasks. 

Exactly how are you running the packages? SQL Agent SSIS task or Command line dtexec? If your SQL Server is 64 bit and the flags are not set it will run in 64bit - if running through command line dtexec this can easily be verified by looking at the task manager for dtexec process - if it has a 32 in front of it it is running in 32bit mode else is running on 64bit.

It' being run via a built job and run by SQL Agent

I've read this thread through a couple of times and I still don't really understand the issue. A SQL Agent job step which runs a package calls a program called DTExec.exe to run the package. DTExec.exe comes in 32- and 64-bit versions, and the one which is executed depends on how you have configured the step in SQL Agent. If you have installed only the 64-bit versions of the drivers on the server, you need to run the package in 64-bit mode.

The issue is that the OP thinks that the packages are not running in 64bit mode as the observed network speed while transferring data is lower than other packages he "knows" are running in 64bit mode.
So the OP wishes to validate that the packages are indeed running in 64bit mode.