skip to main content
OpenEdge Data Management: DataServer for ODBC
The DataServer Tutorial : Preparing to create demonstration databases
 

Preparing to create demonstration databases

Subsequent sections contain tutorials that illustrate using the DataServer utilities to maintain your schema holder. Before you use these tutorials, you must perform some preparatory steps, including creating the demonstration database and schema holder and accessing the DataServer's Utilities menu.
The following lists identifies the basic preliminary steps you must complete to create demonstration databases:
*Install and started your data source. This step depends on your unique environment. Refer to your data source documentation for details.
*Install your DataServer drivers.
*Install the OpenEdge client. Refer to the OpenEdge client-related documentation for details.
To create the demonstration database and schema holder using the OpenEdge DB to ODBC utility:
1. Start the ODBC Data Source Administrator tool for your data source. Refer to Configuring an ODBC driver and registering the data source.
2. Select the appropriate ODBC driver for the schema holder.
3. Select the target ODBC data source for the schema holder. Refer to Configuring a local DataServer and Configuring the remote DataServer.
4. Make any additional selections required by your data source.
5. Specify mysport as the data source name. OpenEdge recognizes the name that you use to register a data source.
You are not required to specify the data source name as mysport. However, identifying the data source name, using this suggested data source name or another one you choose, can help you to distinguish your tutorial data source from all other data sources you set up.
6. From the Start menu on the task bar, select OpenEdge and either select the specific product you want to use to begin your OpenEdge session or type the following command line in Windows:
OpenEdge-install-path
\dlc\bin\prowin32
Starting a local OpenEdge session also automatically starts the local DataServer.
7. Access Data Administration. Create a copy of the Sports database and connect to it.
8. Select DataServerODBC UtilitiesSchema Migration ToolsOpenEdge DB to ODBC to start the OpenEdge DB-to-ODBC Utility. The conversion utility dialog box opens.
9. Specify OpenEdge parameter values as shown in the following table.
Table 22. OpenEdge DB-to-ODBC conversion values
Interface element
Description
Original OpenEdge Database
Accept the name of the connected source database or type the name of a database to which to connect.
Connect parameters for OpenEdge
If you did not specify a new value for the name of the Original OpenEdge Database parameter, do not modify the Connect parameters for OpenEdge parameter.If you did specify a new value, type any additional connect parameters that are necessary.
Name of Schema holder Database
Type the name of the schema holder. The utility creates the schema holder if it does not exist.
ODBC Data Source Name
Type the data source name This is the name of the schema image and the name that you will use to refer to the target database in applications. The data-source name must be different from the name that you typed for the schema holder and different from the name of any other schema image existing in that schema holder.
Foreign DBMS Type
Select the foreign data-source type to which the ODBC driver is connecting.
ODBC Username
Type the user ID.
ODBC User's Password
Type the password.
ODBC connect parameters
See Connecting the DataServer for required connection parameters. For example, -Dsrv might be required in some cases.
Codepage for Schema Image
Accept the default code page.
Collation Name
Enter the OpenEdge name for the collation that your ODBC data source will use. The default is Basic.
Collection/Library
Provide the name of the target location for database objects generated by the migration. This value also becomes the qualifier for retrieving object definitions into the schema holder during the pull phase of the migration. For more information, see Migration considerations for DB2 .
Create RECID Column
Enabled for Sybase and DB2/400 data sources only. Leave checked to create RECID column. When migrating to DB2/400 data source, options are enabled to create a RECID column for all tables or for only those tables that do not have a unique key constraint. Checked by default but only for those tables that do not have a unique key constraint by default when data source is DB2/400.
Load SQL
Leave this toggle box checked.
Create Shadow Columns
If your ODBC data source is case sensitive, and you wish to maintain OpenEdge-compatible, case insensitive behavior, check this box; otherwise, leave blank.
Move Data
Check this toggle box to dump and load data from the OpenEdge database to the target database. Copying data from a large database can take a long time. You can uncheck this toggle box if you want to dump and load data at a more convenient time.This toggle box is available only if the Load SQL toggle box is checked.
Include Defaults
Check to allow default values defined for fields of OpenEdge database.
Note: This option is available only for DB2/400 data sources. If an OpenEdge DATE field has an initial value other than TODAY, then the value will not be pushed to the foreign data source.
For fields width use:
When pushing fields to a foreign data source, you can select one of two primary field format options:
*Width — Uses the value of the _width field in the _field record.
*ABL Format — Compiles with the current default width specified. (default)
If you select the ABL Format option, you have an additional setting to define:
*Expand x(8) to 30 — This setting is on by default to indicate that the format for the character fields defined as x(8) will be created as 30 characters.
Note: You cannot use the Expand x(8) to 30 setting with the Width option.
Note: For a complete description of these Progress-to-ODBC parameters, see Table 26.
Running the utility creates and connects a schema holder and the ODBC data source. It operates as follows:
a. SQL script is generated.
b. SQL that creates the schema is sent to the foreign data manager.
c. The schema is pulled back to the schema holder.
d. The foreign schema holder and the OpenEdge database are compared and all information needed by OpenEdge is applied to the schema holder.
e. If the Move Data toggle box was selected, the data is loaded.
f. The schema holder is disconnected.
g. A message is displayed that tells the user which startup procedure to use to connect.