I'm trying to add an Oracle server as a linked server to SQL Server. I've downloaded and installed Oracle's instant client and ODAC software. However, OraOLEDB.Oracle does not show up in the list of providers in SSMS. My machine is running Windows 7 (64 bit) and MSSQL Server 2008 R2.
I am trying to fix this same issue. I found this detailed set of instructions, however they didn't work for me. I encountered some installation errors with ODAC. Perhaps they can be of help to you though.
Installing 64-bit Oracle ODAC 11.2 to Microsoft SQL Server 2008 R2 x64
http://nampark.wordpress.com/2011/01/20/installing-64-bit-odac-11-2-to-microsoft-sql-server-2008-r2-x64-for-replication/
OraOLEDB provider is not installed with instant client. You have to install the full client.
Related
In one of our company meetings with Microsoft we were advised to use Microsoft SSIS Connectors by Attunity Version 4.0 if we extract data from Oracle. We used to extract the data from Oracle using Oracle Provider for OLE DB.
I have tried to install the recommended components without success. I have oracle clients 32 bits (ODTwithODAC122010.zip) and 64 bits (ODAC122010_x64.zip) installed and then I attempted to install SSIS Attunity Connectors as explained on this post. It's supposed that after the installation I would see the components on the SSIS toolbox (Data Flow section) but no matter what I do they simply don't show up.
I can successfully connect to oracle server using the component we have always used.
My SSIS projects target version is SQL Server 2016. Visual Studio 2015 Enterprise. My OS: Windows 10 Enterprise.
I tried to install v4 32-bit version of the attunity connector and it did not work, I also tried to install v3 64-bit version of the attunity connector and the installation failed because I don't have SQL Server 2014 installed only 2016, which is why I'm supposed to use v4 64-bits.
Any advice from anybody who had an issue like this before?
You need both x86 and x64 versions of the Oracle clients.
And you should install both 4.0 and 5.0 x64 (x86 will be added automatically) versions of Attunity connectors.
After that you should be able (almost guaranteed) to see Attunity connectors in the SSIS Toolbox in VS2015.
Hope this helps.
I had this working on my old 32-bit Windows 7 machine running VS 2010 but am having trouble on my new 64-bit Windows 7 machine running VS 2015.
All I want to do is add an Oracle ODBC connection to Visual Studio's Server Explorer. I get the following error:
I have successfully configured and set up the 32-bit and 64-bit ODBC utilities with ODBC drivers, both pass the "test connection". Also I have set up Oracle SQL Developer to connect to the exact same source using the same credentials and I am able to read from the server in question. Here is the successful connection attempt in the ODBC utility:
I removed the Oracle ODP.NET developer toolset for Visual Studio and now the connections are working. I find Oracle's software incredibly frustrating and hard to use.
Wernfried thank you for taking the time to help.
I installed Visual Studio 2010 on my home computer so I could do a little work from home. After having some issues with SQL Server Express, which got installed by VS2010, I got a copy of SQL Server 2008 R2 from my company. Let me openly admit I know jack about DBA in SQL Server.
At first it sort of worked, but seemed like I needed to rename the database name every time I opened it. Now VS2010 won't even open the connection at all. I keep getting an error stating one is version 661 and the other is 655 and they're not compatible. To make matters worse, I can't even attach the database in SQL Server 2008 R2 anymore.
Any ideas on how to rectify this? Please oversimplify and assume I'm an idiot, because in this case I am.
OK, well apparently VS2010 installs SQL Server 2008 Express on your computer, with which it will happily communicate. Since I then installed SQL Server 2008 R2 after that, 2008 R2 is considered an upgrade and SQL databases are not backwards compatible.
In order to fix this, I installed SQL Server Express 2008 R2 (specifically the SQLEXPRWT_x86_ENU.exe file as that one comes with additional tools) and after a reboot I was able to successfully add the database to my VS project.
NOTE: I did not remove SQL Server 2008 R2, I merely upgraded SQL Server 2008 **Express*.
As an aside, before doing this I could never have VS and SQL Server 2008 R2 open simultaneously. After this upgrade, I can have them both open at the same time which is how it should work.
I'm trying to use the Microsoft Connectors v2.0 for Oracle (https://www.microsoft.com/en-us/download/details.aspx?id=29283) to connect to an Oracle database through SSIS.
I am running Windows 7 SP 1 (64-bit), with Visual Studio 2013 Ultimate. I have installed the connector:
I also have the 32-bit Oracle client installed on my machine for PL/SQL Developer - it works.
But when I create a package in VS 2013 and try to connect to the Oracle DB - I don't have the option to connect to the Oracle source:either by trying to add a new connection through the connection manager or creating a Data Flow Task and dragging the Oracle Source from "Other Sources" within the data flow.
Any suggestions on how to make this work?
Thanks,
Apparently you need the Microsoft Connectors v3.0 for Oracle to work with VS 2013.
Microsoft Connectors v3.0 for Oracle and Teradata
I have Visual Studio.Net 2008 in my Windows XP machine.
I have Oracle 10g client.
As one of my applications uses ODAC, I need to install ODAC now. The latest version of ODAC is ODAC 11.2 Release 3 (11.2.0.2.1) with Oracle Developer Tools for Visual Studio.
My question is, as I already have C:\Oracle\ folder if I install this ODAC again it installs one more oracle_home folder which I dont need.
Could you please suggest how how I can install it?
Thanks
No, you will need to install the version of the Oracle client that the ODAC wants. You also have to decide between 32 bit and 64 bit.
One caution if you are new to Oracle and .Net, you will have to install the oracle client on the server and that creates a lot of problems.
In case someone stills have a similar inquietude ODAC doesn't install an oracle client in the machine, Odac will use the oracle client to communicate with Database Server, so no it won't create a new oracle_home folder.