Enabling SSIS in Visual Studio 2022

If you're using Visual Studio 2022, you will need to install the SQL Server Integration Services Projects extension to use SSIS.

1. Navigate to Extensions > Manage Extensions.
2. In the Manage Extensions window's search box, search for "SQL Server Integration Services Projects 2022" and select the extension in the list.
3. Click Download.
4. Close Visual Studio and run the downloaded Microsoft.DataTools.IntegrationServices.exe installer. Proceed through the installer with default settings.
5. Open Visual Studio. There should now be an "Integration Services Project" project template available.

Adding the Oracle OCI Connection Manager

Create a new connection manager as follows:

1. Create a Visual Studio project with the "Integration Services Project" template.
2. In the project, right-click within the Connection Managers window and select New Connection from the menu.
3. In the Description column, select CData Oracle OCI Connection Manager and click Add...
4. Configure the component as described in the next section.

Alternatively, if you have an existing project and CData Oracle OCI Source or CData Oracle OCI Destination:

1. Right-click your CData Oracle OCI source or destination component in your data flow
2. Select Edit... to open an editor window.
3. Click the New... button next to the Connection manager: dropdown selector to create a connection manager.
4. Configure the component as described in the next section.

Before You Connect

To connect to Oracle, you will first need to update the appropriate environment variable. This variable must contain a folder location that includes the Oracle OCI Library assemblies, which are shipped alongside the component. The correct environment variable depends upon your platform:

• Windows: The native libraries should be on your PATH. Note that the VC++ 2017 Redistributable package is required to load the OCI libraries.
• Mac: The native libraries should be on your DYLIB_LIBRARY_PATH.
• Linux: The native libraries should be on your LD_LIBRARY_PATH.

These native libraries can be found in the lib folder inside the installation directory of the component.

Connecting to Oracle OCI

The following connection types are available:

• Oracle Server
• OracleTNS
• LDAP

Oracle Server

After you have added the appropriate libraries to your PATH, set the following to connect:

• User: The user Id provided for authentication with the Oracle database.
• Password: The password provided for authentication with the Oracle database.
• Port: The port used to connect to the server hosting the Oracle database.
• ServiceName: The service name of the Oracle database. You can obtain this value by querying global_name (select * from global_name) using the Oracle SQL*PLUS command line.
• Server: The host name or IP address of the server hosting the Oracle database.

OracleTNS

Set the following connection properties prior to connecting:

• User: The user Id provided for authentication with the Oracle database.
• Password: The password provided for authentication with the Oracle database.
• DataSource: The Oracle Net Services Name, Connect Descriptor (known also as TNS Connect String), or a connection name that identifies the database to which to connect. You should be able to find these values in your tnsnames.ora file.

For example,

DataSource='(DESCRIPTION=(ADDRESS=(protocol_address_information))(CONNECT_DATA= (SERVICE_NAME=service_name)))'

LDAP

In this scheme, you need to authenticate to the LDAP server. Set the following connection properties to connect:

• User: The user Id provided for authentication with the Oracle database.
• Password: The password provided for authentication with the Oracle database.
• LDAPUri: The LDAP URI used to connect to the LDAP server.
• LDAPUser: The User account for LDAP server.
• LDAPPassword: The password for the LDAP user.

Your connection string should look similar to this:

LDAPUri=ldap://myldap.com:389/SERVICE_EXMPL,cn=OracleContext,dc=example,dc=com; User=ORACLEUSER; Password=OracleUserPassword;

Note that this connection type requires both your Oracle and LDAP usernames and passwords. Your system administrator may allow anonymous LDAP logins, in which case your LDAP username and password are not needed.