OpenEdge Data Management: DataServer for Microsoft SQL Server

Creating a schema holder
• Choose an index that has a narrowly sized key and preferably a single column,
especially since non-clustered indexes use the clustered index to locate rows and
hold the clustered key in their B-tree structure. A composite clustered key can
provide benefits because the part of the table that is also the clustered index does
not need additional space to create the clustered columns and its index.Choose
an index that is reasonably static and does not undergo frequent changes. The
primary key is a good clustered index candidate.
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 Getting Started:
ABL Essentials.
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. If you choose UTF-8 as your schema image code
page, your schema holder’s code page must also be UTF-8.
OpenEdge Data Management: DataServer for Microsoft SQL Server 265