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

> ## 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 MS SQL Server Utilities menu.

> The following lists identifies the basic preliminary steps that you must complete to create demonstration databases:

> - You have installed and started your data source.

> This specific step depends on your unique environment. As necessary, refer to your data source documentation.

> - You have installed your DataServer drivers.

> - You have installed the OpenEdge client. As necessary, refer to the OpenEdge client-related documentation.

> | To create the demonstration database and schema holder using the Progress-to-MSS utility:

> 1. Start the ODBC Data Source Administrator tool for your data source. Refer to the "Configuring an ODBC driver and registering the data source" section.

> 2. Select the appropriate ODBC driver for the schema holder.

> 3. Select the target ODBC data source for the schema holder. Refer to the "Configuring a local DataServer" section and the "Configuring a remote DataServer" section.

> 4. Make any additional selections required by your data source.

> 5. Specify mysport as the data source name. The name that you use to register a data source is the name that OpenEdge recognizes.

> 6. From the Start menu on the taskbar, select OpenEdge and select the specific product you want to use to begin your OpenEdge session or type the following command line in Windows:

>        install-path\dlc\bin\prowin32

> Note: Starting a local OpenEdge session also automatically starts the local DataServer.

> 7. Access the Data Administration tool. Create a copy of the sports database and connect to it.

> 8. Select DataServer MS SQL Server Utilities Schema Migration Tools PROGRESS DB to MS SQL Server to start the Progress-to-MSS Utility.

> 9. Specify Progress-to-MS SQL Server parameter values as noted in Table 7–1.

> Table 7–1: Progress-to-MSS utility
> Interface element | Description
> --- | ---
> Original PROGRESS Database | Accept the default value of sports, which is displayed.
> Connect parameters for PROGRESS | Accept the default value, which specifies the current working database.
> Name of Schema holder Database | Type myholder.
> Logical Database Name | Type name that OpenEdge will use to identify the MS SQL Server database.
> ODBC Data Source Name | Type mysport, which is the name you used when registering the data source.
> Username | Type the user ID for MS SQL Server database.
> User’s Password | Type the password of the user.
> Connect parameters | See Chapter 6, "Connecting the DataServer," for connection parameters.
> Maximum Varchar Length | Enter the maximum size of the `VARCHAR` field. Any size greater will be text. Max size is 8000.
> Codepage | Accept the default code page.
> Collation | Accept the default value.
> Insensitive | Accept the default value.
> Create RECID Field | Check this toggle box to obtain the cursor scrolling capability.
> Load SQL | Leave this box checked to have the generated SQL script loaded into the data source.
> Move Data | Check this toggle box to dump and load data from OpenEdge to MS SQL Server.
> Create Shadow Columns | MS SQL Server is case insensitive by default, and this box is unmodifiable. When SQL Server is configured with a case sensitive code page, this box is available for selection. Selecting it provides case insensitivity compatible with the behavior of an OpenEdge database.
> Include Defaults | Check if you want the OpenEdge initial value used as the default in the SQL script.
> 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. 4GL Format—Compiles with the current default width specified. (default) If you select the 4GL 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 for running while in batch mode, see the "Running the Progress-to-MSS utility in batch mode" section.

> 10. Running the utility creates and connects a schema holder and the MS SQL Server database. It operates as follows:

> 1. SQL script is generated.
> 2. SQL that creates the schema is sent to the MS SQL Server data manager.
> 3. The schema is pulled back to the schema holder.
> 4. The schema holder and the OpenEdge database are compared and all information needed by OpenEdge is applied to the schema holder.
> 5. Data is loaded if selected.
> 6. The schema holder is disconnected.
> 7. A message is displayed that tells the user which startup procedure to use to connect. Additionally, the entered connect information is also stored in the db record which the DataServer can use to automatically connect.

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