We've recently installed SQL Server 2016 on development including SSIS, and we're in the process of migrating our work over to this new server. Part of this work involves migrating packages that involve interfacing with other DBMSs. To do that, I need to install connector drivers again. I know that for past versions of SSIS you had to install both the 32 and 64 bit versions of ODBC connector drivers, as parts of SSIS ran in 32-bit no matter what while other parts might run in 64-bit. Does this behavior and requirement hold for SSIS 2016, or does it suffice to just install the 64-bit drivers now?

  • Was your requirement for 32 bit due to the other systems or because of SQL? I've had to use 32 bit in the past, but it was due to the systems I was connecting to, not due to SQL.
    – Jason B.
    Aug 11, 2016 at 18:25
  • For my edification, can you provide an example of a driver that allows you install both a 32 and a 64 bit side by side? Most of the ones I've dealt with block installation if the other bit is detected
    – billinkc
    Aug 11, 2016 at 18:32
  • 1
    It's been awhile, a year or so, since I last had to work with configuring SSIS components but I distinctly remember having to install both the 32 and 64 bit versions of Oracle instant client to get everything to work. We were running SSIS 2012 at that point. It is possible to install both Oracle versions side by side but it takes some effort. realfiction.net/2009/11/26/… Aug 11, 2016 at 18:39

1 Answer 1


In the case of DBMSs that only offer ODBC connectors to interface with SSIS (Among other things) the answer is that only the 32-bit connector needs to be installed to make an ODBC data source that SSIS 2016 can recognize. For my environment this was the case with IBM Informix and Progress OpenEdge.

In the case of Oracle the prevailing wisdom I read back when I was working with SSIS 2012 still applies. I had to install both the 32 and 64 bit instant clients, configure symbolic links so that Windows could leverage both of them as it needed, and make the appropriate TNS files and environment variables for the Oracle connector to function.

MySQL worked with just the most recent, 64-bit .NET connector. The same applied to Teradata. It seems that only ODBC connectors and Oracle need 32-bit access.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.