Release 10.1A: OpenEdge Data Management:
DataServer for Microsoft SQL Server

> ## Creating a schema holder

> | To create the schema holder:

> 1. From the Data Administration main menu, select DataServer MS SQL Server 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 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 OpenEdge Development: Progress 4GL Handbook .

> Note: If you place the schema from a second MS SQL Server database 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.

> 3. In the Code Page field, type the name of the code page for the schema holder. The name must be the OpenEdge name for the code page that the data source uses. The default is iso8859–1.

> Table 7–3 lists the most common MS SQL Server database code pages and the equivalent OpenEdge names.

> Table 7–3: MS SQL Server and OpenEdge code pages
> MS SQL Server Code page | OpenEdge equivalent
> --- | ---
> iso_1 | iso8859–1 (default schema-holder code page)
> cp850 | ibm850

> If you use a code page that OpenEdge does not support, you must supply a conversion table that translates between the OpenEdge client code page and the code page that your data source uses. For a complete discussion of code pages, see OpenEdge Development: Internationalizing Applications .

> 4. In the Collation field, enter the name of the collation rule to use. The default is Basic. See the "Code pages" section for a discussion of collation issues to consider.

> 5. Type the connection parameters in the Connection Parameters field.

> See Chapter 6, "Connecting the DataServer," for a description of the required and optional connection parameters.

> 6. In the ODBC Data Source Name field, type the name that you used when you registered the data source with the ODBC administration tool.

> 7. Choose OK. The utility prompts you for your data source user ID and password. If they are required by the MS SQL Server data source and you did not provide them in the Connection Parameters field (see Step 5), enter a data-source user ID and password combination that has select privileges for the system objects listed in the "Permission requirements" section and read access to other database objects that the schema holder will include.

> 8. Choose OK. When the DataServer connects to the MS SQL Server database, it reads information about data source objects. The following dialog box appears:

> You can select tables based on the object name, owner/library information, and qualifier. For example, you can specify A* in the Object Name field to list all the tables whose names begin with A or a.

> 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.)

> 9. Choose OK. OpenEdge displays a list of the data source objects that you can include in the schema holder, as shown:

> 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.

> 10. Select the objects that you want to include in the schema holder and choose OK. The DataServer reads information about the 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 objects that you select.

> For each 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 errors, 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 Data Dictionary. See the "Defining the ROWID" section for instructions. For additional information, see the "Indexes and sorting" section.

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