skip to main content
OpenEdge Data Management: DataServer for ODBC
Troubleshooting : Tuning your environment with the -Dsrv startup parameter : Using ODBC and DataServer options : Schema import: The PRGRS_NO_INDEX option
 
Schema import: The PRGRS_NO_INDEX option
For ODBC drivers that are not fully ODBC Level 1 compliant, one potential trouble area is data-source index information. The DataServer requires a unique index for each table and view in order to scroll, update, delete, and create rows. If the process of fetching schema information fails, you can reconnect to the data source using the -Dsrv PRGRS_NO_INDEX,1 startup parameter to specify that index information is not automatically imported. Instead, you create a unique index definition manually by using the Data Dictionary. This guarantees that you can create a unique index for a combination of fields that truly have a unique index in the data source. Note that creating the index does not create an index in the ODBC data source; it marks the DataServer for the unique key for that table.