6. OpenLink ODBC Driver for Ingres (Express Edition)

6.1. OpenLink ODBC Driver for Ingres (Express Edition) for Mac OS X

6.1.1. Installation Guide

The OpenLink ODBC Driver for Ingres (Express Edition) is distributed as a Disk image (DMG) file. Simply double click on the disk image 'mul6eing.dmg' to extract the installer mpkg file:

Figure: 6.1.1.1.

Double click on the mpkg file to run the installer and following the on screen instriuction as indicated below to complete the installation:

Figure: 6.1.1.2.

Installer Welcome Dialog for the OpenLink ODBC Driver for Ingres (Express Edition):

Figure: 6.1.1.3.

Please review the readme file for installation requirements and known issues:

Figure: 6.1.1.4.

Please read the software license agreement before continuing your installation:

Figure: 6.1.1.5.

Select destination volume for driver installation:

Figure: 6.1.1.6.

Choose to perform a custome or default installation of the driver:

Figure: 6.1.1.7.

If you chose the custom option select which of the components below are to be installed:

Figure: 6.1.1.8.

The Software must be installed as a user with Administrative privileges on the machine:

Figure: 6.1.1.9.

After the driver has been installed you will be prompted for a license file. If a license file already exists on the machine then select the 'use exisiting file' option. A trial (try) or full (buy) license can be obtain by selecting the 'try and buy' option which loads our online try and buy web page:

Figure: 6.1.1.10.

To obtain the trial license you must be a registered user on the OpenLink Web site and login with the username (e-mail address) and password for that user. Click on the 'Shop' link to visit our online shop cart to purchases a full license if required:

Figure: 6.1.1.11.

Click on the 'download license' button to obtain the license file immediately and save to your desktop. Alternatively an auto e-mail will be sent to the registered users e-mail address with a link to their OpenLink Data Space (ODS) where all trial and full license files will be stored in the Briefcase for download at a later date.

Figure: 6.1.1.12.

Select the license file to be used for the installation:

Figure: 6.1.1.13.

Installation is complete:

Figure: 6.1.1.14.

6.1.2. Configuration

To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:

Figure: 6.1.2.1.

Click on the add button to Choose the ODBC Driver the DSN should be created for:

Figure: 6.1.2.2.

Choose the OpenLink Ingres Driver (Express Edition) v6.0 from the list of available drivers:

Figure: 6.1.2.3.

In the Data Source tab, select a suitable DSN name and optional description for the Data Source to be created:

Figure: 6.1.2.4.

The Connection Tab requests the minimum paramters required to make a connection to the target database:

Figure: 6.1.2.5.

• Hostname - the hostname of the server on which the Ingres Node is running
• PortName - the Ingres instance Node name
• Database - the ase name of a valid database on the Node
• Username - the name of a valid Ingres user
• Advanced - additional optional configuration parameters:

As indiacted above the paramters of the options and preferences tabs are not required for a basic connection:

Figure: 6.1.2.7.

• Row Buffer Size - This attribute specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.
• Hide Login Dialog - Suppress the ODBC "Username" and "Password" login dialog box when interacting with your ODBC DSN from within an ODBC compliant application.
• Read Only connection - Specify whether the connection is to be read-only. Make sure the checkbox is unchecked to request a read/write connection.
• Drop Catalog from Meta calls - Enable this option to have the catalog name not appear for tables, views and procedures when requesting database meta-data.
• Drop Schema from Meta calls - Enable this option to have the schema-name not appear for tables, views and procedures when requesting database meta-data.
• SQLStatistics disabled - Check this box to have SQLStatistics() return an empty resultset. Use this if the underlying database does not support retrieving statistics about a table (e.g. what indexes there are on it).
• No support of quoted identifier - If it is set, the call SQLGetInfo for 'SQL_IDENTIFIER_QUOTE_CHAR' will return the space (" "). It can be used if DBMS doesn't support quoted SQL such as select * from "account"
• No support of search string escape - If it is set, the call SQLGetInfo for 'SQL_LIKE_ESCAPE_CLAUSE' will return the space character (" "). It can be used if DBMS doesn't support SQL escape patterns
• Patch of NULL size of SQL_CHAR - If set this option overrides the size of SQL_CHAR column type returned by the database with the value set in the text box (in bytes). With the default value of 0 the driver uses the size returned by the database.
• SQL_DBMS Name - Manually override the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is know to be required for products like Microsoft InfoPath for which the return the value should be "SQL Server".

Figure: 6.1.2.8.

• Initialization SQL - Lets you specify a file containing SQL statements that will be run against the database upon connection, automatically.
• Cursor Sensitivity - Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same - deleted rows don't appear in the rowset, updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the 'High Cursor Sensitivity' checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database.
• MaxRows Override - Allows you to define a limit on the maximum number of rows to returned from a query. The default value of 0 means no limit.
• Disable AutoCommit - Change the default commit behaviour of the OpenLink Lite Driver. The default mode is AutoCommit mode (box unchecked).
• Disable Rowset Size Limit - Disable the limitation enforced by the cursor library. The limitation is enforced by default to prevent the Driver claiming all available memory in the event that a resultset is generated from an erroneous query is very large. The limit is normally never reached.
• Defer fetching of long data - Defer fetching of LONG (BINARY, BLOB etc.) data unless explicitly requested in query. This provides significant performance increase when fields in query does not include LONG data fields.
• Multiple Active Statements Emulation - Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver.

Click on the 'Test Data Source' button to make a connection to the database to verify connectivity:

Figure: 6.1.2.9.

Enter a vaild username and pasword for the database:

Figure: 6.1.2.10.

A successful connection to the database has been made:

Figure: 6.1.2.11.