Connection Options
Go Up to Configuring Feature Options
The Connection tab of the Options Editor lets you specify common connectivity options and provides access to DBMS-specific options.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
The table below describes the options and functionality on the Connection tab:
Option | Description | Default |
---|---|---|
Login Timeout |
Specifies the number of seconds that the application should wait for a response to a connection request from server. If server does not respond within the specified period, the application aborts the connection and returns an error message. |
30 |
Query Timeout |
Specifies the number of seconds that the application should wait for a response to a query from the server. If the server does not respond within the specified period, the application terminates its query process and returns an error. |
0 |
Host Name |
Name of the client computer. |
Local name |
See the following topics for DBMS platform-specific options:
- Connection Options - DB2
- Connection Options - MySQL
- Connection Options - PostgreSQL
- Connection Options - Sybase
- Connection Option - Sybase IQ
- Connection Option - SQL Server
- Connection Options - Oracle
Contents
Connection Options - DB2
The Connection > DB2 tab of the Options Editor lets you specify DBMS-specific connection options.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
- Note: For more general connectivity options, see Connection Options.
Group | Setting | Description |
---|---|---|
Default Driver Selection |
By default, when you register a datasource, the native driver is automatically selected as the default connection option. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option. | |
Connect using JDBC instead of the DB2 CLI driver |
For platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option. For platforms for which no native driver is available, this check box is disabled. | |
JDBC driver to use |
If multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default. | |
Assign to all disconnected Datasources |
This control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the DB2 CLI driver setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform. |
Connection Options - MySQL
The Connection > MyQSL tab of the Options Editor lets you specify DBMS-specific connection options.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
- Note: For more general connectivity options, see Connection Options.
Group | Setting | Description |
---|---|---|
Default Driver Selection |
By default, when you register a datasource, the native driver is automatically selected as the default connection option. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option. | |
Connect using JDBC instead of the MySQL Connector/ODBC driver |
For platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option. For platforms for which no native driver is available, this check box is disabled. | |
JDBC driver to use |
If multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default. | |
Assign to all disconnected Datasources |
This control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the MySQL Connector/ODBC driver setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform. |
Connection Options - PostgreSQL
The Connection > PostgreSQL tab of the Options Editor lets you specify DBMS-specific connection options.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
- Note: For more general connectivity options, see Connection Options.
Group | Setting | Description |
---|---|---|
Default Driver Selection |
By default, when you register a datasource, the native driver is automatically selected as the default connection option. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option. | |
Connect using JDBC instead of the PostgreSQL ODBC driver |
For platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option. For platforms for which no native driver is available, this check box is disabled. | |
JDBC driver to use |
If multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default. | |
Assign to all disconnected Datasources |
This control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the PostgreSQL ODBC driver setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform. |
Connection Options - Sybase
The Connection > Sybase tab of the Options Editor lets you select an installed client other than the active/default client version for IDERA driver connections. It also lets you override default client/server settings.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
- Note: For more general connectivity options, see Connection Options.
Group | Setting | Description |
---|---|---|
Use Quoted Identifiers |
If you plan to use delimited identifiers, select this option. | |
Sybase Open Client Selection |
This group of controls apply only to use of the IDERA drivers with native Sybase clients. | |
Enable Client Selection |
Selecting this check box lets you override the default/active Sybase client specified by the SYBASE, SYBASE_OCS, and/or SYBROOT environment variables. This control enables and disables the Client Home Directory and Client OCS Directory controls. | |
Client Home Directory |
Browse to the root directory of the client to be used. | |
Client OCS Directory |
Select the OCS- directory corresponding to the client version that you want to use. | |
Connection Settings |
SQL INI File |
Browse to locate and select the specific, SQL.INI-formatted file containing server-configuration information. The file does not have to be named SQL.INI. |
Packet Size, Max Connections, and Client Character Set |
These settings let you create a set of default parameters used in setting up connections to Sybase ASE datasources. These settings can be overridden when registering a Sybase ASE datasource. For details, see Providing Sybase ASE Connection Information When Registering Datasources. | |
Default Driver Selection |
By default, when you register a datasource, the native driver is automatically selected as the default connection option. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option. | |
Connect using JDBC instead of the Sybase Open Client |
For platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option. For platforms for which no native driver is available, this check box is disabled. | |
JDBC driver to use |
If multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default. | |
Assign to all disconnected Datasources |
This control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the Sybase Open Client setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform. |
Connection Options - Sybase IQ
The Connection > Sybase IQ tab of the Options Editor lets you specify DBMS-specific connection options.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
- Note: For more general connectivity options, see Connection Options.
Setting | Description | |
---|---|---|
Use Quoted Identifiers |
If you plan to use delimited identifiers, select this option. | |
Default Driver Selection |
By default, when you register a datasource, the native driver is automatically selected as the default connection option. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option. | |
Connect using JDBC instead of the Sybase IQ ODBC Driver |
For platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option. For platforms for which no native driver is available, this check box is disabled. | |
JDBC driver to use |
If multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default. | |
Assign to all disconnected Datasources |
This control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the Sybase IQ ODBC Driver setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform. |
Connection Options - SQL Server
The Connection > SQL Server tab of the Options Editor lets you specify DBMS-specific connection options.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
- Note: For more general connectivity options, see Connection Options.
Setting | Description | |
---|---|---|
SQL Server Native Client Selection |
These controls let you specify a default native driver. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. | |
Enable Client Selection |
Where multiple native drivers are supported, this check box enables selection of a native client to use as the default option. | |
Clients |
Select the native client to be used as default. | |
Use Quoted Identifiers |
If you plan to use delimited identifiers, select this option. | |
Connection Settings |
Packet Size |
This control lets you specify a default packet size parameter used with SQL Server connections. This setting can be overridden when registering a SQL Server datasource. For details, see Providing SQL Server Connection Information When Registering Datasources. |
Default Driver Selection |
By default, when you register a datasource, the native driver is automatically selected as the default connection option. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option. | |
Connect using JDBC instead of the SQL Server Native Client |
For platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option. For platforms for which no native driver is available, this check box is disabled. | |
JDBC driver to use |
If multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default. | |
Assign to all disconnected Datasources |
This control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the DB2 CLI driver setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform. |
Connection Options - Oracle
The Connection > Oracle tab of the Options Editor lets you select an installed client other than the active/default client version for IDERA driver connections. It also lets you override default client/server settings.
- Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
- Note: For more general connectivity options, see Connection Options.
Group | Setting | Description |
---|---|---|
Hide time portion of DATE datatype if zero |
If selected, the time portion (HH:MM:SS) of DATE datatype results are suppressed in the ISQL Editor’s Results window, if the time portion is all zeroes. | |
OCI Client Selection |
This group of controls apply only to use of the IDERA drivers with native Oracle clients. If no client is specified using these controls, the following sequence is used in determining the client to use for Oracle connections. - The driver specified in the ORACLE_HOME environment variable - The first driver found in the PATH environment variable - The bundled Oracle Instant Client driver (v. 11) | |
Enable Client Selection |
Selecting this check box lets you override the default/active client specified by Oracle environment variables. This control enables and disables the Oracle Home control. | |
Oracle Home |
Select the directory of the Oracle client you wish to use. | |
TNSNAMES.ORA |
Directory Path of Oracle configuration files |
Browse to locate and select the directory containing the TNSNAMES.ORA file to use. Ensure that no file name is included with the path. If no file is specified using this control, the following sequence is used in determining the TNSNAMES.ORA file to use for Oracle connections. -The directory specified in the TNS_ADMIN environment variable - The directory specified in the TNS_ADMIN key at the top level in HKLM\SOFTWARE\ORACLE - The directory specified in the TNS_ADMIN key in the client subkey (HOME or KEY_ prefixed) corresponding to the value of the ORACLE_HOME (if there is a particular client specified by the user, its TNS_ADMIN subkey will be used if present) - The directory ORACLE_HOME\NETWORK\ADMIN (if there is a particular client specified by the user, ORACLE_HOME is the client's full path) - The directory ORACLE_HOME\net80\ADMIN (if there is a particular client specified by the user, ORACLE_HOME is the client's full path) - All directories in PATH environment variable |
Default Driver Selection |
By default, when you register a datasource, the native driver is automatically selected as the default connection option. NOTE: For details on native driver and JDBC driver support, see the ReadMe file selecting View > Release Notes. The controls in this group let you specify one of the installed or packaged DBMS platform-specific JDBC drivers as the default connection option. | |
Connect using JDBC instead of the OCI client |
For platforms for which a native driver is supported, this check box enables selection of a JDBC driver as the default connection option. For platforms for which no native driver is available, this check box is disabled. | |
JDBC driver to use |
If multiple JDBC drivers are available for this platform, this control lets you select the specific JDBC driver to use as the default. | |
Assign to all disconnected Datasources |
This control lets you assign either the native driver or the currently selected JDBC driver as the connection option for all datasources defined on the relevant DBMS platform that are currently not connected. If the Connect using JDBC instead of the OCI client setting is selected, all disconnected datasources are assigned the driver selected from the JDBC driver to use list as the connection option. Otherwise, the native driver is assigned to all disconnected datasources on this DBMS platform. |