Progress
DataServer
for ODBC Guide


Creating a Schema Holder

Follow these steps to create the schema holder:

  1. From the Data Administration main menu, select DataServer ODBC Utilities Create DataServer Schema. The following dialog box appears:
  2. In the Logical Database Name field, type the name that you will use to connect to your ODBC data source and refer to it in your programming applications. This name must be different from the schema holder name. For more information on database names, see the database access chapter in the Progress Programming Handbook.
  3. NOTE: If you place the schema from a second ODBC data source into a schema holder, the second schema must have a different logical database name from the first schema. The schema holder has one physical name, but each schema that it contains must have a different logical name.

  4. In the Code Page field, type the name of the code page for the schema holder. The name must be the Progress name for the code page that the data source uses. The default is iso8859–1.
  5. Table 3–4 lists the most common ODBC data-source code pages and the equivalent Progress names.

    Table 3–4: ODBC Data-source and Progress Code Pages 
    ODBC Data-Source Code Page
    Progress Equivalent
    iso_1
    iso8859–1
    (default schema-holder code page)
    cp850
    ibm850

    If you use a code page that Progress does not support, you must supply a conversion table that translates between the Progress client code page and the code page that your data source uses. For a complete discussion of code pages, see the Progress Internationalization Guide.

  6. Type the connection parameters in the Connection Parameters field.
  7. See "Connecting the DataServer," for a description of the required and optional connection parameters.

  8. In the ODBC Data Source Name field, type the name that you used when you registered the data source with the ODBC administration tool.
  9. Choose OK. The utility prompts you for your data-source user ID and password. If they are required by the non-Progress data source and you did not provide them in the Connection Parameters field (see Step 4), enter a data-source user ID and password combination that has select privileges for the system objects listed in the “Establishing Permissions” section and read access to other database objects that the schema holder will include.
  10. Choose OK. When the DataServer connects to the ODBC data source, it reads information about data-source objects. The following dialog box appears:
  11. You can select tables based on the object name, owner name, and qualifier. For example, you can specify A* in the Object Name field to list all the tables whose names begin with A.

    Note that for DB2 data sources only, you must type the name of the DB2 database in the Object Owner field. If the DB2 database name is different from the authorization ID for the tables being selected, type the authorization ID in the Object Owner field.

    NOTE: Progress Software Corporation recommends that you do not specify an entry that consists exclusively of wild cards for each of the three entry fields in the dialog box. An entry that consists exclusively of wild cards might degrade the performance of the database when you perform a schema pull. (It will include system catalog files from the data source not typically included in user databases.)

  12. Choose OK. Progress displays a list of the data-source objects that you can include in the schema holder:
  13. If you specified all wild cards as your table-selection criteria, the list might also include system-owned objects, which you do not have to include in the schema holder.

  14. Select the objects that you want to include in the schema holder and choose OK. The DataServer reads information about the data-source objects that you select and loads their data definitions into the schema holder. The time that this process takes depends on the size and number of data-source objects that you select.
  15. For each data-source table, the DataServer attempts to select an index to support the Progress ROWID. If an appropriate index does not exist, the DataServer issues the warning, “Please check warnings and messages in the file ds_upd.e.” The ds_upd.e file lists the objects that do not support ROWID. You can change the DataServer’s selection of an index to support ROWID by using the Progress Data Dictionary. See the "Defining the ROWID" section in "The DataServer Tutorial," for instructions. For additional information, see the "Indexes" and "ROWID Function" sections, respectively, in Programming Considerations."


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095