Progress
DataServer for
Microsoft SQL Server
Guide


Running the Progress-to-MSS Utility

The Progress-to-MSS utility runs on Windows with a DataServer accessing SQL Server™ through an ODBC driver.

You can run the utility interactively from Windows or NT, Unix, or in batch mode.

Running the Progress-to-MSS Utility Interactively

To run the Progress-to-MSS utility interactively, follow these steps:

  1. Create a target SQL Server™. You must use an empty target data source when you run the Progress-to-MSS utility.
  2. Configure your ODBC driver to connect to your new target data source.
  3. Start the Progress client and connect to the Progress database that you want to migrate to the target data source.
  4. NOTE: For a DBE (double-byte enabled) DataServer application, you must specify the Internal Code Page (-cpinternal) and Stream Code Page (-cpstream) parameters when you start the Progress client. The values that you specify for these parameters must match the code page that the target data source uses.

  5. From the Data Administration tool, choose DataServer MS SQL Server Utilities Schema Migration Tools PROGRESS DB to MS SQL Server.
  6. The following screen appears:
  7. It prompts you for the information described in Table 5–4.

    Table 5–4: Progress-to-MSS Utility
    Interface Element
    Description
    Name of the Original Progress Database
    Accept the default value of sports, which is displayed.
    Other connect parameters for Progress Database
    Accept the default value, which specifies the current working database.
    Enter name of Schema holder Database
    Type myholder.
    Enter the Logical Database name
    Type the name that Progress will use to identify the SQL Server™ database.
    Enter name for Database in the ODBC data source
    Type mysport, which is the name you used when registering the data source.
    Enter the Username
    Type the user ID for SQL Server™.
    Enter user’s Password
    Type the password of the user.
    Enter other connect parameters
    See "Connecting the DataServer," for connection parameters.
    Enter codepage for Schema Image
    Accept the default code page.
    Maximum length of VARCHAR field
    Enter the maximum size of the VARCHAR field. Any size greater will be text. Max size is 8000.
    Create RECID field
    If this parameter is available for your data source type, check this toggle box to obtain the Extended 4GL 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 Progress to SQL Server™.
    Create Shadow Columns
    SQL Server is case insensitive by default. Leave unchecked unless the default has been changed and you want Progress behavior.
    Create Desc Index
    SQL Server™ does not support Descending Indexes. So any indexes that have descending components are skipped. If this box is checked, all indexes are created as ascending.
    Include Defaults
    Check if you want the Progress initial value used as the default in the SQL script.
    Use Fields SQL Width Column
    If your Progress database contains data that is larger than the display format, you can check this toggle box. Change the SQL width field in the Data Dictionary to the proper size. The utility will use the SQL width field instead of the display format.

If you want a complete migration of your Progress database to a target data source, you must enter information in all appropriate fields and check all appropriate toggle boxes.

The utility creates a schema holder, updates the empty target data source that you created to contain the objects stored in your Progress database, and creates a startup procedure that you can use to connect your schema holder. The startup procedure derives its name from the logical name for your target database. For example, if you specified “sports” as the logical data source name, the utility creates the csports.p startup procedure.

Running the Progress-to-MSS Utility in Batch Mode

To run the Progress-to-MSS utility in batch mode, follow these steps:

  1. Create a target SQL Server™ database. You must use an empty target data source when you run the Progress-to-MSS utility.
  2. Configure your ODBC driver to connect to your new target data source.
  3. On your client machine, pass parameters to the utility by setting the environment variables listed in Table 5–5.
    Table 5–5: Progress-to-MSS Utility Batch Parameters
    Environment Variable

    Description
    PRODBNAME
    Specifies the source Progress database name.
    PROCONPARMS
    Specifies parameters for the connection to the source Progress database.
    SHDBNAME
    Specifies the new schema-holder name.
    MSSDBNAME
    Specify ODBC data source name.
    MSSPDBNAME
    Specify logical database name.
    MSSUSERNAME
    Specifies the user name for the target data source.
    MSSPASSWORD
    Specifies the password of the user for the target data source.
    MSSCONPARMS
    Specifies additional connection parameters for the schema holder.
    MSSCODEPAGE
    Specifies the Progress name for the code page that the ODBC data source uses. By default, the code page for a schema holder is ibm850. You can leave this field blank and use the Change Code page utility to add the code page information for the schema holder later.
    VARLENGTH
    Total number of characters a VARCHAR can have. Any field whose format is greater that will be defined as a text field. Maximum is 8000.
    SQLWIDTH
    If present, use the Progress file _WIDTH field size instead of calculating length by using the display format.
    DESCIDX
    If present, create an index that contains descending components as ascending since SQL Server™ does not support descending indexes.
    LOADSQL
    Allows you to specify whether you want the utility to create the schema in your empty SQL Server™ database. Specify YES to enable this behavior.
    MOVEDATA
    Allows you to specify whether to populate the database. Specify YES to dump and load data or NO to not populate the database. For example, you might specify NO if your database is large, and you want to dump and load data at a more convenient time. The default is NO.
  4. Enter the following commands to set and export environment variables at the system prompt:
  5. NOTE: You might need to append the Progress libraries to your PROPATH environment variable in order for the executable to find .p or .r files.

    PRODBNAME=db-name; export PRODBNAME
    PROCONPARMS="-1 -i"
    SHDBNAME=schema-holder-name; export SHDBNAME
    .
    .
    .
    pro -b -p prodict/mss/protomss.p 
    

  6. Run protomss.p.

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