Setting up a connection between an On-Premises SQL Server Database Instance to an Oracle ADB on the Oracle Cloud
![SQL Developer to Oracle ADB]( "Creating SS_USER in Oracle")
2. I install Oracle Client and configure connectivity to the ADB database with the Wallet information
![sqlnet.ora]( "Configuring Connectivity to Oracle ADB")
![tnsnames.ora]( "Service Entry in tnsnames.ora")
3. Optionally re-register the OraOLEDB18.DLL file (using CMD as Administrator) (you might also need to reboot your Windows or restart the SQL Server Instance)
![CMD as Administrator]( "Register the OraOLEDB18.DLL file")
4. Define the Linked Server in SQL Server (using SSMS)
![Oracle OLEDB Provider]( "Configure \"Allow inprocess\"")
![Linked Server Configuration Pag]( "Defining the Linked Server to Oracle ADB")
![Linked Server Security Configuration]( "Configure username/password for Oracle ADB")
5. Test Connectivity
![Test Connectivity Option for Linked Server]( "Verify that Connection is successful")
![SSMS Query and Results Pane]( "Run Queries against Oracle via Linked Server")
Strong Caveat : This is only a POC. Most organisations would NOT allow an open direct connection between an On-Premises Database and and External Site (whether a Database or any other Service).
1. On my Free-Tier Oracle ADB, I login as the ADMIN user and configure a new database account "ss_user"
2. I install Oracle Client and configure connectivity to the ADB database with the Wallet information
(for detailed instructions see the Oracle Cloud documentation here). {I used an 18c Client on Windows to connect to 19c ADB, simply because I already and 18c client and didn't want to wait to download the 19c client}
4. Define the Linked Server in SQL Server (using SSMS)
6 Run queries against from SSMS
