an ODBC driver?
To do this, execute the ODBC driver file distribution, and follow the on-screen instructions.
The install program starts the Easysoft License Manager, because you cannot use your Easysoft product until a license is obtained.
The following types of license are available:
Complete the Name, E-Mail Address, and Company fields.
The E-Mail Address must be the same as the address used to register and download from the Easysoft web site or you will be unable to obtain trial licenses.
You're asked for a license type.
The License Manager asks what software you are licensing. Select your product from the drop-down list and then choose Next.
The License Manager requests your authorization code.
Enter the authorization code and then choose Next.
The License Manager then sends a request to the Easysoft license server to activate your license key automatically. This is the quickest method and results in your details being entered immediately into our support database.
Each of these methods involves providing Easysoft with information including your machine number (a number unique to your machine) and then waiting to receive your license key.
Instead of emailing your details to Easysoft, you can enter them directly at the Easysoft web site and your license key will be emailed to you automatically.
To use this method, choose View Request, and then visit:
In the licensing page, enter your machine number (and authorization code for a purchased license), choose Submit and your license key will be emailed to you.
When you receive the license key, you can activate it either by double-clicking the email attachment or by choosing Enter License on the License Manager main screen and pasting the license key into the dialog box.
The installation is complete.
Before you can use the Oracle ODBC driver to connect your SQL Server to Oracle, you need to configure an ODBC data source. An ODBC data source stores the connection details for the target database (in this case, Oracle) and the ODBC driver that is required to connect to it (in this case, the Oracle ODBC driver).
You configure ODBC data sources in ODBC Data Source Administrator, which is included with Windows. There is both a 64-bit and 32-bit version of ODBC Data Source Administrator.
If you have the 64-bit version of SQL Server and want to use a linked server with the Oracle ODBC driver, your application is 64-bit. You need to run 64-bit version of ODBC Data Source Administrator. To do this, open Administrative Tools in Control Panel, and then open Data Sources (ODBC). (On Windows Server 2003 and earlier, the Control Panel applet that launches ODBC Data Source Administrator is labelled Data Sources. On Windows 8 and later, the Control Panel applet is labelled ODBC Data Sources (64-bit).)
If you have the 32-bit version of SQL Server or want to use SSIS with the Oracle ODBC driver, your application is 32-bit. You need to run 32-bit version of ODBC Data Source Administrator. To do this, in the Windows Run dialog box, enter:
%windir%\syswow64\odbcad32.exe
Use ODBC Data Source Administrator to create a Oracle ODBC driver data source:
Setting | Value |
---|---|
DSN | ORACLEWP |
User Name | The name of your Oracle user. |
Password | The password for your Oracle user. |
Server | The host name or IP address of the machine on which Oracle is running. |
SID | The service name that identifies the database you want to connect to. For Oracle Database XE, the service name is XE. |
These steps show you how to use a linked server to work with Oracle data, just as if you were working with data stored in a SQL Server table:
You need to log on with an account that is a member of the SQL Server sysadmin
fixed server role to create a linked server.
ORACLEWP
.SQL Server verifies the linked server by testing the connection.
A four-part table name has the format:
server_name.[database_name].[schema_name].table_name.
For Oracle you need to omit the database name. For example:
SELECT * FROM ORACLEWP..SYSTEM.mytable
OPENQUERY
function. For example:
SELECT * FROM OPENQUERY(ORACLEWP, 'SELECT * FROM mytable')
SQL Server sends pass-through queries as uninterpreted query strings to the Oracle ODBC driver. This means that SQL Server does not apply any kind of logic to the query or try to estimate what that query will do.