Progress
Version 9
Product Update Bulletin
Progress Version 9.1D DataServer For ODBC
The Progress Version 9.1D DataServer for ODBC contains the following enhancement over previous versions:
Collation Table Support For ODBC
Version 9.1D of the DataServer for ODBC now allows the user to specify the collation table that should be used through the Create/Modify Database Record for DataServer Schema dialog box. You can access the Collation option through the Data Administration tool, and select DataServer
ODBC Utilities
Create DataServer Schema. The dialog box shown in Figure A–6 opens.
Figure A–6: Create/Modify Database Record For DataServer Schema Dialog Box
![]()
The collation table that the user specifies must be defined in the
convmap.dat
file or the user will receive an error message stating that the combination between the code page and the table does not exist.For more information on collation tables, see the Progress Internationalization Guide .
The user can also specify the Collation table in the PROGRESS DB to ODBC Conversion screen. To access this utility from the Data Administration tool, choose DataServer
ODBC Utilities
Schema Migration Tools
PROGRESS DB to ODBC.
The dialog box shown in Figure A–7 opens.
Figure A–7: PROGRESS DB To ODBC Conversion Dialog Box
![]()
Alternative No NameServer Support For ODBC
In prior versions of the DataServer for Microsoft ODBC, you can connect through the Progress Explorer without using the NameServer by providing a special value of “none” to the
-DataService
connection parameter. Now, in Progress Version 9.1D, to indicate that the NameServer should not be used, the DataServer for ODBC can use the-DirectConnect
connection parameter. If the-DirectConnect
connection parameter is specified, then the-H
and-S
parameters are interpreted as the host and port of the broker. However, unlike connecting directly to the broker with the-DataService
connection parameter, using the -DirectConnect parameter makes the-H
and -S
parameters optional. If-H
is not provided, it defaults to “localhost”. If-S
is not specified, it defaults to 4444. If-DirectConnect
is specified, the-DataService
is ignored.Dynamic Find Feature For ODBC
In Progress Version 9.1D, the DataServer for ODBC executes Dynamic Find statements like a FOR FIRST or FOR LAST statement. This should provide increased performance over a typical FIND FIRST or FIND LAST statement. In particular, the NO-LOCK Dynamic Find statements are executed using a single SQL SELECT statement instead of the two SQL SELECT statements required by a typical FIND statement.
QUOTER Function For ODBC
The QUOTER function can be useful for quoting values or handling embedded quotes when building SQL statements that will be passed into the send-sql-statement stored procedure. For more information on the QUOTER function, see "Progress 4GL Language Reference" in this bulletin and the Progress Programming Handbook .
DataServer (–Dsrv) Startup Parameter Option For ODBC
RECID Buffer size: The ZPRGRS_RECID_BUF_SIZE,xxx Option
The Progress Version 9.1D DataServer for ODBC tries to select a unique index over each table defined in your schema holder to support the Progress RECID/ROWID functions. RECID functionality enables backward and forward scrolling in the DataServer product.
The RECID buffer is used to store key information about the unique index selected to support RECID. The default RECID buffer size is 245 bytes. The space is used dynamically to allocate the RECID buffer for a given record. The RECID buffer size needs to be large enough to contain all the key information regarding the unique index. If the unique index selected is a composite of many columns and/or contains large column names, the RECID key information might exceed the RECID buffer size and issue error message 2090.
If you exceed the RECID buffer limit, Progress first recommends that you try to find an alternative unique index with a smaller number of key fields. This should help to improve performance during record access as well. You can change the RECID index in the Progress dictionary by selecting the “DataServer” button from the Table Properties of the table in your schema holder.
If it is not possible to change the selected RECID unique index for the table that is over running the buffer, you can expand the area by setting the startup option as follows:
Where xxx is the new size of the area in bytes.
You can expand the RECID buffer size to a maximum of 1000 bytes. The minimum size is 44 bytes. The algorithm to determine your adjusted size is as follows:
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |