skip to main content
OpenEdge Data Management: DataServer for ODBC
Connecting the DataServer : Connecting a schema holder
 

Connecting a schema holder

As described previously, connection can take place automatically using the information that you enter when you create a schema holder. In addition, OpenEdge provides the following techniques for connecting to a schema holder:
*Use the Data Dictionary or Data Administration. From the main menu, select Database > Connect and supply the schema holder's physical name and the appropriate connection parameters. You connect to the data source when you select it as your working database.You cannot use the Utilities > Auto–Connect option to connect to an ODBC data source.
*Use the ABL CONNECT statement (see its reference entry in OpenEdge Development: ABL Reference. A CONNECT statement must first list the schema holder and related connection parameters, then the ODBC data source and related parameters.
For example, this command connects a schema holder named holder and an ODBC-supported data source named odbdemo:
CONNECT odbholder -db odbdemo -dt ODBC.
You can use combinations of different connection techniques. For example, you can connect the schema holder at startup, then connect to the DataServer using the CONNECT statement. Any combination of connection techniques works, as long as you first connect to the schema holder and then the ODBC data source.
If you are not updating the schema holder, you can specify the Read-only (-RO) connection parameter to enhance DataServer performance.
If you connect to the schema holder and the ODBC data source in a single startup command or connection statement, be sure to specify parameters that affect the schema holder before the Database Name (-db) parameter. Specify only those parameters that affect the ODBC data source connection after the -db parameter.
The following section explains how to connect both a schema holder and an ODBC data source when you start up OpenEdge.
In this section: 
* Connecting a schema holder at startup
* Unsupported connection parameters
* Special connection issues
* Query tuning with connection and startup parameters
* Binding with connection and startup parameters
* Analyzing performance
* Local schema caching