My development machine runs Windows 7 64-bit, with Visual Studio 2017 Community Edition, v 15.9.3, and with SSDT for Visual Studio 2017 (15.8.2). My SQL Server box runs Windows Server 2012 R2 Standard, with SQL Server 2012 SP 4 (build 11.0.7001.0). I use
SQL Server Management Studio v 17.4 on my Windows 7 development machine.
I have Oracle's SQL Developer installed and working fine: I can write and execute queries. Now I need to create an SSIS package that does the same thing: execute a SELECT query on Oracle, then load it into a SQL Server table. There are hundreds of different
drivers and tools on the Oracle and Microsoft sites, but so far none of them work -- where "work" means "allow me to execute the package in Visual Studio and also deploy and execute the SSIS package on SQL Server." I get myriads of different
error messages, depending on which drivers I try. I have no problem with the SQL Server connection, of course -- only the Oracle connection.
My hope is that there is a driver I can install on my development machine using nothing but (the appropriate bitness of) regsvr32 and a corresponding driver I can install on my SQL Server box using nothing but Regsvr32. I don't want hundreds of java files,
development tools, setup.exe's that stuff thousands of entries in my registry. I just want to register a single dll (or maybe two if you tell me I need both 32 and 64 bit drivers). After registering the DLL, I need it to appear in the drop-down list of providers
at the top of the Connection Manager window in Visual Studio (the one that shows various .Net Provders and .Net Providers for OleDb.
Surely thousands of people have figured out how to do this -- but days of Googling inevitably lead down the path of "install the Oracle Instant Client" or "use the Oracle Universal Installer" or some such -- and these are like throwing
a fragmentation grenade into the registry -- and still don't work (see my above definition of "work").
Any suggestions?
Leigh Webber