Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
for ODBC
Progress Supplement
Release 6.0
March 2009
© 2009 Progress Software Corporation. All rights reserved. Printed in the U.S.A.
DataDirect, DataDirect Connect, DataDirect Connect64, DataDirect Spy, DataDirect Test, DataDirect XML Converters,
DataDirect XQuery, OpenAccess, SequeLink, Stylus Studio, and SupportLink are trademarks or registered trademarks
of Progress Software Corporation or one of its subsidiaries or affiliates in the United States and other countries. Java
and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the
United States and other countries. MySQL and MySQL Enterprise are registered trademarks of MySQL AB in the
United States, the European Union and other countries.
Other company or product names mentioned herein may be trademarks or registered trademarks of their respective
companies.
DataDirect products for the Microsoft SQL Server database:
These products contain a licensed implementation of the Microsoft TDS Protocol.
DataDirect Connect for ODBC, DataDirect Connect64 for ODBC, and DataDirect SequeLink include:
ICU Copyright © 1995-2003 International Business Machines Corporation and others. All rights reserved. Permission
is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all
copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting
documentation.
Software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http:/www.openssl.org/). Copyright ©
1998-2006 The OpenSSL Project. All rights reserved. And Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All
rights reserved.
DataDirect SequeLink includes:
Portions created by Eric Young are Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All Rights Reserved.
OpenLDAP, Copyright © 1999-2003 The OpenLDAP Foundation, Redwood City, California, US. All rights reserved.
DataDirect OpenAccess SDK client for ODBC, DataDirect OpenAccess SDK client for ADO, DataDirect Open Access
SDK client for JDBC, and DataDirect OpenAccess SDK server include: DataDirect SequeLink.
No part of this publication, with the exception of the software product user documentation contained in electronic
format, may be copied, photocopied, reproduced, transmitted, transcribed, or reduced to any electronic medium or
machine-readable form without prior written consent of DataDirect Technologies.
Licensees may duplicate the software product user documentation contained on a CD-ROM or DVD, but only to the
extent necessary to support the users authorized access to the software under the license agreement. Any
reproduction of the documentation, regardless of whether the documentation is reproduced in whole or in part,
must be accompanied by this copyright statement in its entirety, without modification.
3
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Product Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Using this Supplement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Conventions Used in this Supplement . . . . . . . . . . . . . . . . . . . 9
Typographical Conventions. . . . . . . . . . . . . . . . . . . . . . . . . 9
Environment-Specific Information . . . . . . . . . . . . . . . . . . . 10
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Preface
Windows
http://www.datadirect.com/products/odbc/matrix/connectodbc.htm (32-bit)
http://www.datadirect.com/products/odbc64/matrix/connect64odbc.htm (64-bit)
NOTE: This supplement may refer the reader to Web URLs for
more information about specific topics, and may include Web
URLs not maintained by DataDirect Technologies. Because it is the
nature of Web content to change frequently, DataDirect
Technologies can guarantee only that the URLs referenced in this
supplement were correct at the time of publishing.
Typographical Conventions
Convention Explanation
italics Introduces new terms with which you may not
be familiar, and is used occasionally for
emphasis.
bold Emphasizes important information. Also
indicates button, menu, and icon names on
which you can act. For example, click Next.
UPPERCASE Indicates keys or key combinations that you can
use. For example, press the ENTER key.
Convention Explanation
brackets [ ] Indicates optional items. For example, in the
following statement: SELECT [DISTINCT],
DISTINCT is an optional keyword.
Environment-Specific Information
The drivers are supported in the Windows, UNIX, and Linux
environments. When the information provided is not applicable
to all supported environments, the following symbols are used to
identify that information:
The UNIX symbol signifies text that is applicable only to UNIX and
Linux.
HTML Version
All of these books are placed on your system as HTML-based
online help during a normal installation of DataDirect Connect
for ODBC. They are located in the help subdirectory of the product
installation directory. To use the help, you must have an Internet
browser installed.
install_dir/help/help.htm
browser_exe install_dir/help/help.htm
After the browser opens, the left pane displays the Table of
Contents, Index, and Search tabs for the entire documentation
library. When you have opened the main screen of the help
system in your browser, you can bookmark it in the browser for
quick access later.
NOTE: Security features set in your browser can prevent the help
system from launching. A security warning message is displayed.
Often, the warning message provides instructions for unblocking
the help system for the current session. To allow the help system
to launch without encountering a security warning message, the
security settings in your browser can be modified. Check with
your system administrator before disabling any security features.
Help is also available from the setup dialog box for each driver.
When you click Help, your browser opens to the correct topic in
the help system, without opening the help Table of Contents. A
grey toolbar appears at the top of the browser window.
This tool bar contains previous and next navigation buttons. If,
after viewing the help topic, you want to see the entire library,
click:
on the left side of the toolbar, which opens the left pane and
displays the Table of Contents, Index, and Search tabs.
PDF Version
A PDF version of this supplement is provided in the Progress
driver package. You can view the PDF documentation using the
Adobe Acrobat Reader.
http://support.datadirect.com
http://www.datadirect.com/support/eval_help/index.ssp
■ The DataDirect product and the version that you are using.
■ The type and version of the operating system where you have
installed your DataDirect product.
When you define and configure a data source, you store default
connection values for the driver that are used each time you
connect to a particular database. You can change these defaults
by modifying the data source.
NOTE: The General tab displays only fields that are required
for creating a data source. The fields on all other tabs are
optional, unless noted otherwise.
2 The following two options appear on the General tab of all
driver Setup dialog boxes:
3 On the driver Setup dialog box, click OK. The values you have
specified are saved and are the defaults used when you
connect to the data source. You can change these defaults by
using the previously described procedure to modify your data
source. You can override these defaults by connecting to the
data source using a connection string with alternate values.
See individual driver chapters for information about using
connection strings.
Environment Variables
The first step in setting up and configuring the drivers for use is
to set several environment variables. The following procedures
require that you have the appropriate permissions to modify
your environment and to read, write, and execute various files.
You must log in as a user with full r/w/x permissions recursively
on the entire DataDirect Connect for ODBC installation directory.
echo $SHELL
source ./odbc.csh
. ./odbc.sh
env
ODBCINI
DataDirect Connect for ODBC Setup installs in the product
installation directory a default system information file, named
odbc.ini, that contains data sources. See “The ivtestlib Tool” on
page 23 for an explanation of the odbc.ini file. The system
administrator can choose to rename the file and/or move it to
another location. In either case, the environment variable
ODBCINI must be set to point to the fully qualified path name of
the system information file.
ODBCINI=/opt/odbc/odbc.ini;export ODBCINI
ODBCINST
DataDirect Connect for ODBC Setup installs in the product
installation directory a default file, named odbcinst.ini, for use
with DSN-less connections. See “DSN-less Connections” on
page 33 for an explanation of the odbcinst.ini file. The system
administrator can choose to rename the file or move it to
another location. In either case, the environment variable
ODBCINST must be set to point to the fully qualified path name
of the odbcinst.ini file.
DD_INSTALLDIR
This variable provides the driver with the location of the product
installation directory so that it can access support files.
DD_INSTALLDIR must be set to point to the fully qualified path
name of the installation directory.
DD_INSTALLDIR=/opt/odbc;export DD_INSTALLDIR
2 The driver checks the odbc.ini or the odbcinst.ini files for the
InstallDir keyword (see “Configuration Through the System
Information File” on page 25 for a description of the
InstallDir keyword)
ivtestlib /opt/odbc/lib/ivoe1024.so
NOTE: On Solaris, AIX, and Linux, the full path to the driver does
not have to be specified for ivtestlib. The HP-UX version of
ivtestlib, however, requires the full path.
The second section of the file is named [ODBC File DSN] and
includes one keyword:
This keyword defines the path of the default location for file
data sources (see “File Data Sources” on page 36).
The third section of the file is named [ODBC] and includes several
keywords:
[ODBC]
IANAAppCodePage=4
InstallDir=ODBCHOME
Trace=0
TraceFile=odbctrace.out
TraceDll=ODBCHOME/lib/odbctrac.so
Tracing
ODBC tracing allows you to trace calls to ODBC drivers and
create a log of the traces for troubleshooting purposes.
Trace=1
TraceFile=odbctrace.out
TraceDll=ODBCHOME/lib/odbctrac.so
To specify the path and name of the trace log file, enter it as the
value for TraceFile. If no location is specified, the trace log
resides in the working directory of the application you are using.
shared object instead, enter the path and name of the shared
object as the value for TraceDll.
[Progress OpenEdge]
Driver=ODBCHOME/lib/ivpro1024.so
Description=DataDirect 6.0 Progress OpenEdge
DatabaseName=<database_name>
EnableTimestampWithTimezone=1
HostName=<Progress_server>
LogonID=
Password=
PortNumber=<Progress_server_port>
[Progress SQL92]
Driver=ODBCHOME/lib/ivpro924.so
Description=DataDirect 6.0 Progress SQL92
DatabaseName=<database_name>
HostName=<Progress_server>
LogonID=
Password=
PortNumber=<Progress_server_port>
[ODBC]
IANAAppCodePage=4
InstallDir=ODBCHOME
Trace=0
TraceFile=odbctrace.out
TraceDll=ODBCHOME/lib/odbctrac.so
First, open the default odbc.ini. Then, open the progodbc.ini file
from which you can copy Progress data source descriptions and
definitions.
6 After making all modifications, save the odbc.ini file and close
the text editor.
Translators
DataDirect provides a sample translator named "OEM to ANSI"
that provides a framework for coding a translation library. Refer
to the readme.trn file in the /src/trn subdirectory in the product
installation directory for details.
For example:
For example:
DSN-less Connections
Connections to a data source can be made via a connection
string without referring to a data source name (DSN-less
connections). This is done by specifying the "DRIVER=" keyword
instead of the "DSN=" keyword in a connection string, as
outlined in the ODBC specification. A file named odbcinst.ini
must exist when the driver encounters DRIVER= in a connection
string.
The final section of the file is named [ODBC]. The [ODBC] section in
the odbcinst.ini file fulfills the same purpose in DSN-less
connections as the [ODBC] section in the odbc.ini file does for
data source connections. See “Configuration Through the System
Information File” on page 25 for a description of the other
keywords this section.
NOTE: The odbcinst.ini file and the odbc.ini file include an [ODBC]
section. If the information in these two sections is not the same,
the values in the odbc.ini [ODBC] section override those of the
odbcinst.ini [ODBC] section.
[ODBC]
#This section must contain values for DSN-less connections
#if no odbc.ini file exists. If an odbc.ini file exists,
#the values from that [ODBC] section are used.
For example, a file data source for the Progress Wire Protocol
driver would be similar to the following:
[ODBC]
Driver=DataDirect 6.0 Progress OpenEdge Wire Protocol
PortNumber=2055
HostName=LOCALHOST
LogonID=JOHN
DatabaseName=Payroll
FILEDSN=/home/users/john/filedsn/Progresswp2.dsn
FILEDSN=/home/users/john/filedsn/Progresswp2.dsn;UID=james;PWD=test01
See the readme file shipped with your DataDirect product for
the file name of the Progress OpenEdge Wire Protocol driver.
Driver Requirements
There are no client requirements for the Progress OpenEdge
Wire Protocol driver.
NOTE: The General tab displays only fields that are required for
creating a data source. The fields on all other tabs are optional,
unless noted otherwise.
Port Number: The system port number setup for the database
listener process.
Click OK.
1 In the Host Name field, type the name of the system where
the database is stored.
DSN=data_source_name[;attribute=value[;attribute=value]...]
FILEDSN=filename.dsn[;attribute=value[;attribute=value]...]
DRIVER=[{]driver_name[}][;attribute=value[;attribute=value]
...]
Table 3-1 gives the long and short names for each attribute, as
well as a description. You can specify either long or short names
in the connection string. Connection string attribute names are
the same as the option names on the driver Setup dialog box
tabs unless otherwise noted. The connection string attribute
name does not have spaces between the words. For example, the
connection string attribute name ApplicationUsingThreads is
equivalent to the option name Application Using Threads.
The defaults listed in the table are initial defaults that apply
when no value is specified in either the data source definition or
in the connection string. If you specified a value for the attribute
when configuring the data source, that value is the default.
DSN=PROGRESS;DB=PAYROLL;UID=JOHN;PWD=XYZZY
FILEDSN=ProgOpen.dsn;DB=PAYROLL;UID=JOHN;PWD=XYZZY
Attribute Description
ArraySize (AS) The number of rows the driver retrieves from the server for a
fetch. This is not the number of rows given to the user. The
initial default is 50 rows.
You should set this connection string attribute to the
approximate number of rows being fetched. This reduces the
number of round trips on the network, thereby increasing
performance.
This attribute can affect performance. See "Performance
Considerations" on page 50 for details.
The equivalent Setup dialog box option is Fetch Array Size.
DatabaseName (DB) The name of the database to which you want to connect.
DataSourceName (DSN) A string that identifies a Progress OpenEdge data source
configuration. Examples include Accounting or PROG-Serv1.
DefaultIsolationLevel (DIL) DefaultIsolationLevel={READ COMMITTED | READ
UNCOMMITED | REPEATABLE READ | SERIALIZABLE}. Specifies
the default isolation level for concurrent transactions. The
initial default is REPEATABLE READ.
EnableTimestampWith EnableTimestampWithTimezone={0 | 1}. Determines whether
Timezone (ETWT) the driver exposes timestamps with timezones to the
application.
When set to 1 (the initial default), timestamps with
timezones are exposed to the application, and the format is
YYYY-MM-DD HH:MM:SS.SSS+HH:MM.
The equivalent Setup dialog box option is Enable Timestamp
with Timezone.
HostName (HOST) The name of the system where the database is stored.
Table 3-1. Progress OpenEdge Wire Protocol Connection String Attributes (cont.)
IANAAppCodePage (IACP) For a list of valid values for this attribute, refer to the
DataDirect Connect for ODBC and Connect XE for ODBC
Reference. You need to set this attribute if your application
is not Unicode-enabled and/or if your database character set
is not Unicode (refer to the DataDirect Connect for ODBC and
Connect XE for ODBC Reference for details). The value you
specify must match the database character encoding and the
system locale.
The Driver Manager checks for the value of
IANAAppCodePage in the following order:
■ In the connection string
■ In the Data Source section of the system information file
(odbc.ini)
■ In the ODBC section of the system information file
(odbc.ini)
If no IANAAppCodePage value is found, the driver uses the
default value of 4 (ISO 8859-1 Latin-1).
LogonID (UID) The default logon ID (user name) used to connect to your
Progress OpenEdge database. This ID is case-sensitive.
The equivalent Setup dialog box option is User ID.
Password (PWD) A case-sensitive password.
PortNumber (PORT) The system port number setup for the database listener
process.
UseWideCharacterTypes UseWideCharacterTypes={0 | 1}. Determines whether
(UWCT) character data types are described to the application as
SQL_CHAR or SQL_WCHAR.
When set to 0 (the initial default), character data types are
described to the application as SQL_CHAR.
When set to 1, character data types are described to the
application as SQL_WCHAR.
Performance Considerations
The following connection options can enhance driver
performance. You can also enhance performance through
efficient application design. Refer to the DataDirect Connect for
ODBC and Connect XE for ODBC Reference for details.
The option names found on the tabs of the driver Setup dialog
box are the same as the connection string attribute names unless
otherwise noted in parentheses. The connection string attribute
name does not have spaces between the words. For example, the
option name Application Using Threads is equivalent to the
connection string attribute name ApplicationUsingThreads.
Data Types
Table 3-2 shows how the Progress OpenEdge data types are
mapped to the standard ODBC data types.
OpenEdge ODBC
Bigint SQL_BIGINT
Binary SQL_BINARY
Bit SQL_BIT
Blob SQL_LONGVARBINARY
Clob SQL_LONGVARCHAR
Date SQL_TYPE_DATE
Decimal SQL_DECIMAL
Double precision SQL_DOUBLE
Float SQL_FLOAT
Integer SQL_INTEGER
Lvarbinary SQL_LONGVARBINARY
Lvarchar SQL_LONGVARCHAR
Real SQL_FLOAT
Smallint SQL_SMALLINT
Time SQL_TYPE_TIME
Timestamp SQL_TYPE_TIMESTAMP
Timestamp with Time Zone SQL_CHAR
Tinyint SQL_TINYINT
Varbinary SQL_VARBINARY
Varchar SQL_VARCHAR
Unicode Support
This driver supports the Unicode ODBC W (Wide) function calls,
such as SQLConnectW. This allows the Driver Manager to transmit
these calls directly to the driver. Otherwise, the Driver Manager
would incur the additional overhead of converting the W calls to
ANSI function calls, and vice versa.
Refer to the DataDirect Connect for ODBC and Connect XE for ODBC
Reference for related details about UTF-16 applications on UNIX
and Linux, and for a more detailed explanation of the role of
Unicode in internationalization and localization.
Threading
The Progress drivers operate on a Thread Per Connect basis.
See the readme file shipped with your DataDirect product for
the file name of the Progress OpenEdge driver.
Driver Requirements
To access a Progress OpenEdge Release 10 database with the
OpenEdge driver, your client must have the Progress
OpenEdge 10.0B client software installed.
Before using the driver, you must set the DLC environment
variable to your OpenEdge DLC directory. For example:
set DLC=C:\OpenEdge
NOTE: The General tab displays only fields that are required
for creating a data source. The fields on all other tabs are
optional, unless noted otherwise.
Port Number: The system port number setup for the database
listener process.
DSN=data_source_name[;attribute=value[;attribute=value]...]
FILEDSN=filename.dsn[;attribute=value[;attribute=value]...]
DRIVER=[{]driver_name[}][;attribute=value[;attribute=value]
...]
Table 4-1 gives the long and short names for each attribute, as
well as a description. You can specify either long or short names
in the connection string. Connection string attribute names are
the same as the option names on the driver Setup dialog box
tabs unless otherwise noted. The connection string attribute
name does not have spaces between the words. For example, the
The defaults listed in the table are initial defaults that apply
when no value is specified in either the data source definition or
in the connection string. If you specified a value for the attribute
when configuring the data source, that value is the default.
DSN=PROGRESS;DB=PAYROLL;UID=JOHN;PWD=XYZZY
Attribute Description
ArraySize (AS) The number of rows the driver retrieves from the server for a
fetch. This is not the number of rows given to the user. The
initial default is 50 rows.
You should set this connection string attribute to the
approximate number of rows being fetched. This reduces the
number of round trips on the network, thereby increasing
performance.
This attribute can affect performance. See "Performance
Considerations" on page 66 for details.
The equivalent Setup dialog box option is Fetch Array Size.
DatabaseName (DB) The name of the database to which you want to connect.
DataSourceName (DSN) A string that identifies a Progress OpenEdge data source
configuration. Examples include Accounting or PROG-Serv1.
LogonID (UID) The default logon ID (user name) used to connect to your
Progress OpenEdge database. This ID is case-sensitive.
The equivalent Setup dialog box option is User ID.
Performance Considerations
The following connection options can enhance driver
performance. You can also enhance performance through
efficient application design. Refer to the DataDirect Connect for
ODBC and Connect XE for ODBC Reference for details.
The option names found on the tabs of the driver Setup dialog
box are the same as the connection string attribute names unless
otherwise noted in parentheses. The connection string attribute
name does not have spaces between the words. For example, the
option name Application Using Threads is equivalent to the
connection string attribute name ApplicationUsingThreads.
NOTE: The ideal setting for your application will vary. To calculate
the ideal setting for this option, you must know the size in bytes
of the rows that you are fetching and the size in bytes of your
Network Packet. Then, you must calculate the number of rows
that will fit in your Network Packet, leaving space for packet
overhead. For example, suppose your Network Packet size is 1024
bytes and the row size is 8 bytes. Dividing 1024 by 8 equals 128;
however, the ideal setting for Fetch Array Size is 127, not 128,
because the number of rows times the row size must be slightly
smaller than the Network Packet size.
Data Types
Table 4-2 shows how the Progress OpenEdge data types are
mapped to the standard ODBC data types.
OpenEdge ODBC
Bigint SQL_BIGINT
Binary SQL_BINARY
Bit SQL_BIT
Blob SQL_LONGVARBINARY
Char SQL_CHAR
Clob SQL_LONGVARCHAR
Date SQL_TYPE_DATE
Decimal SQL_DECIMAL
Double precision SQL_DOUBLE
Float SQL_FLOAT
Integer SQL_INTEGER
Lvarbinary SQL_LONGVARBINARY
Lvarchar SQL_LONGVARCHAR
Real SQL_FLOAT
Smallint SQL_SMALLINT
Time SQL_TYPE_TIME
Timestamp SQL_TYPE_TIMESTAMP
Timestamp with Time Zone SQL_CHAR
Tinyint SQL_TINYINT
Varbinary SQL_VARBINARY
Varchar SQL_VARCHAR
Threading
The Progress drivers operate on a Thread Per Connect basis.
See the readme file shipped with your DataDirect product for
the file name of the Progress SQL92 driver.
Driver Requirements
To access a Progress Version 9.1D or 9.1E database with the
Progress SQL92 driver, your system must have the following
software installed:
Before using the driver, you must set the DLC environment
variable to your Progress DLC directory. For example:
set DLC=C:\PROGRESS
NOTE: The General tab displays only fields that are required
for creating a data source. The fields on all other tabs are
optional, unless noted otherwise.
Port Number: The system port number setup for the database
listener process.
DSN=data_source_name[;attribute=value[;attribute=value]...]
FILEDSN=filename.dsn[;attribute=value[;attribute=value]...]
DRIVER=[{]driver_name[}][;attribute=value[;attribute=value]
...]
Table 5-1 gives the long and short names for each attribute, as
well as a description. You can specify either long or short names
in the connection string. Connection string attribute names are
the same as the option names on the driver Setup dialog box tabs
unless otherwise noted. The connection string attribute name
does not have spaces between the words. For example, the
The defaults listed in the table are initial defaults that apply
when no value is specified in either the data source definition or
in the connection string. If you specified a value for the attribute
when configuring the data source, that value is the default.
DSN=PROGRESS;DB=PAYROLL;UID=JOHN;PWD=XYZZY
FILEDSN=Prog92.dsn;DB=PAYROLL;UID=JOHN;PWD=XYZZY
Attribute Description
ArraySize (AS) The number of rows the driver retrieves from the server for a
fetch. This is not the number of rows given to the user. The
initial default is 50 rows.
You should set this connection string attribute to the
approximate number of rows being fetched. This reduces the
number of round trips on the network, thereby increasing
performance.
This attribute can affect performance. See "Performance
Considerations" on page 82 for details.
The equivalent Setup dialog box option is Fetch Array Size.
DatabaseName (DB) The name of the database to which you want to connect.
DataSourceName (DSN) A string that identifies a Progress data source configuration.
Examples include Accounting or PROG-Serv1.
DefaultIsolationLevel (DIL) DefaultIsolationLevel={READ COMMITTED | READ
UNCOMMITED | REPEATABLE READ | SERIALIZABLE}. Specifies
the default isolation level for concurrent transactions. The
initial default is REPEATABLE READ.
HostName (HOST) The name of the system where the database is stored.
IANAAppCodePage (IACP) For a list of valid values for this attribute, refer to the
DataDirect Connect for ODBC and Connect XE for ODBC
Reference. You need to set this attribute if your application
is not Unicode-enabled and/or if your database character set
is not Unicode (refer to the DataDirect Connect for ODBC and
Connect XE for ODBC Reference for details). The value you
specify must match the database character encoding and the
system locale.
The Driver Manager checks for the value of
IANAAppCodePage in the following order:
■ In the connection string
■ In the Data Source section of the system information file
(odbc.ini)
■ In the ODBC section of the system information file
(odbc.ini)
If no IANAAppCodePage value is found, the driver uses the
default value of 4 (ISO 8859-1 Latin-1).
LogonID (UID) The default logon ID (user name) used to connect to your
Progress SQL92 database. This ID is case-sensitive.
The equivalent Setup dialog box option is User ID.
Password (PWD) A case-sensitive password.
PortNumber The system port number setup for the database listener
(PORT) process.
Performance Considerations
The following connection options can enhance driver
performance. You can also enhance performance through
efficient application design. Refer to the DataDirect Connect for
ODBC and Connect XE for ODBC Reference for details.
The option names found on the tabs of the driver Setup dialog
box are the same as the connection string attribute names unless
otherwise noted in parentheses. The connection string attribute
name does not have spaces between the words. For example, the
option name Application Using Threads is equivalent to the
connection string attribute name ApplicationUsingThreads.
NOTE: The ideal setting for your application will vary. To calculate
the ideal setting for this option, you must know the size in bytes
of the rows that you are fetching and the size in bytes of your
Network Packet. Then, you must calculate the number of rows
that will fit in your Network Packet, leaving space for packet
overhead. For example, suppose your Network Packet size is 1024
bytes and the row size is 8 bytes. Dividing 1024 by 8 equals 128;
however, the ideal setting for Fetch Array Size is 127, not 128,
because the number of rows times the row size must be slightly
smaller than the Network Packet size.
Data Types
Table 5-2 shows how the Progress SQL92 data types are mapped
to the standard ODBC data types.
Threading
The Progress drivers operate on a Thread Per Connect basis.
Index
E Progress OpenEdge 65
Progress OpenEdge Wire Protocol 49
Progress SQL92 81
EnableTimestamp
Progress OpenEdge 65
Progress OpenEdge Wire Protocol 48
environment-specific information 10 O
ODBC conformance
H Progress OpenEdge 68
Progress OpenEdge Wire Protocol 53
Progress SQL92 84
HostName OEM to ANSI translation 31
Progress OpenEdge 65
Progress OpenEdge Wire Protocol 48
Progress SQL92 80
HP-UX
See UNIX and Linux
P
Password
Progress OpenEdge 66
I Progress OpenEdge Wire Protocol 49
Progress SQL92 81
PortNumber
IANAAppCodePage Progress OpenEdge 66
Progress OpenEdge 65 Progress OpenEdge Wire Protocol 49
Progress OpenEdge Wire Protocol 49 Progress SQL92 81
Progress SQL92 81 Progress OpenEdge driver
isolation levels See also Progress OpenEdge Wire Protocol
Progress OpenEdge 68 driver
Progress OpenEdge Wire Protocol 52 connection string attributes 64
Progress SQL92 84 connections supported 69
ivtestlib tool 23 data source
configuring 56
connecting via connection string 63
connecting via logon dialog box 62
L data types 67
driver requirements 55
Linux isolation levels 68
See UNIX and Linux locking levels 68
locking levels ODBC conformance 68
Progress OpenEdge 68 statements supported 69
Progress OpenEdge Wire Protocol 52 threading 69
Progress SQL92 84
LogonID
S W
Solaris Windows
See UNIX and Linux drivers
statements supported Progress OpenEdge 55
Progress OpenEdge 69 Progress OpenEdge Wire Protocol 39
Progress OpenEdge Wire Protocol 53 Progress SQL92 71
Progress SQL92 84
SupportLink 13
system information file (.odbc.ini) 24