OpenEdge Data Management: DataServer for Microsoft SQL Server

Chapter 6: Connecting the DataServer
You can create a parameter file for each database:
• For a local DataServer, the parameter file must contain the -db parameter and can
optionally contain the -Dsrv, -U, and -P connection parameters, depending on the
requirements of the data service.
• For a remote DataServer, the same parameter conditions apply as for a local
DataServer. In addition, a remote connection must contain the -H and -S
connection parameters.
You can add more startup and connection parameters than the ones listed—these are
the typical parameters. For a complete list of parameters and for information on how to
create a parameter file, see OpenEdge Deployment: Startup Command and Parameter
Reference.
Using a local DataServer configuration
Use the following general command syntax to start OpenEdge:
• In single-user mode
• In a local DataServer configuration
• With a local schema holder connected
• With a MS SQL Server database connected
prowin32 schema-holder-name -1 -db datasrc-name -dt MSS
-ld mss-logical-dbname -U userID -P password -Dsrv
qt_debug,EXTENDED
You can type these commands on the command line of a program item property box.
The following examples start OpenEdge in a local DataServer configuration:
• The schema holder’s physical name is mssholder and it is read-only.
• The physical data source name and the MS SQL Server database name is
sports.
• The data source type is MSS (Microsoft SQL Server).
• The logical database name is mysport.
• The user ID is bob.
• The password is bobpass.
• Assorted -Dsrv options are specified.
prowin32 mssholder -RO -db sports -dt MSS -ld mysport -U bob -P bobpass
-Dsrv qt_debug,EXTENDED
222 OpenEdge Data Management: DataServer for Microsoft SQL Server