Try OpenEdge Now
skip to main content
DataServer for Microsoft SQL Server
Connecting the DataServer : Connecting a schema holder : Connecting a schema holder at startup
 

Connecting a schema holder at startup

OpenEdge supports connection parameters that you can use to connect both the OpenEdge schema holder and a MS SQL Server database at startup. These parameters control how your system connects to a database. If the DataServer runs in a remote configuration, your startup command or parameter file always includes parameters that control networking options.
The following table describes the database connection parameters that you use when you connect to a schema holder and a MS SQL Server database through the DataServer.
Table 34. DataServer connection parameters
Parameter
Status
Description
Database Type MSS
(-dt MSS)
Optional
Specifies that the type of the target data source is MS SQL Server.
If not specified, the server will resolve the database type.
Physical Database Name
(-db)
Required
Indicates the name by which OpenEdge recognizes the MS SQL Server database to which you want to connect. This name must match the name that you used when you registered the data source as a MS SQL Server database.
Logical Database Name
(-ld)
Optional
Specifies the logical name of the MS SQL Server database. This is the name that you use to refer to the data source in your applications. You must use this parameter only when the logical data source name differs from its physical name. This name should match the logical database name that you defined in your schema holder.
For example, your applications might refer to the MS SQL Server demo database as mydemo. In this case, the physical name is demo, and the logical name is mydemo.
If not specified, the logical database name is assumed to be the same as the physical name. An error will be generated if the physical name and logical name do not match when this parameter is omitted.
Host Name
(-H)
Required for remote DataServer
Indicates the name of the Windows host machine in the network.
Service Name
(-S)
Required for remote DataServer
Indicates the name of the service you are calling. If you use NameServer with OpenEdge Management or OpenEdge Explorer, specify the service name or port number on the host machine where the NameServer resides. If you are using ProBroker or OpenEdge Management/OpenEdge Explorer without a NameServer, specify the service name or port number on the host machine where the broker resides.
User ID
(-U)
Required
Supplies the login name that the DataServer uses to log into the MS SQL Server database.
Explorer Redirection
(-Dsrv SVUB,1)
Required for OpenEdge Management or OpenEdge Explorer connections
Redirects connection logic to OpenEdge Management or OpenEdge Explorer instead of ProBroker. This parameter must be set if the -DataService connection parameter is to also be used for connectivity. For more information see Starting and stopping a broker process from OpenEdge Management/OpenEdge Explorer and connecting a client. Also refer to Using MS SQL Server and DataServer options.
Data Service
(-DataService)
Required for OpenEdge Management or OpenEdge Explorer connections
Specifies the data service the NameServer uses. For more information, see Starting and stopping a broker process from OpenEdge Management/OpenEdge Explorer and connecting a client.
Direct Connect
(-DirectConnect)
Optional. For use with OpenEdge Management or OpenEdge Explorer connections
Instructs the client to bypass the controlling NameServer and connect directly to the MS SQL Server DataServer Broker. If not specified, the connection is made through the NameServer.
Password
(-P)
Required
Supplies the password that the DataServer uses to log into the MS SQL Server database. Different login name and password combinations allow for different levels of user privileges.
Single-User Mode
(-1)
Optional
Specifies that a schema holder is used in single-user mode. Single-User Mode is the default unless a server is started for the schema holder.
If not specified, -RO or remote connection parameters are required.
Read-Only
(-RO)
Optional
Specifies that a schema holder is read-only. Connecting a schema holder as read-only increases processing speed at client startup time. It also allows multiple client processes on the same machine to access the schema holder without starting additional server processes.
If not specified, the database is opened for update as well as read access.
Local Cache
(-cache)
Optional
Specifies that you are using a local cache file for the schema holder. Create the cache file with the SAVE CACHE COMPLETE statement.
If not specified, no cache file is used.
DataServer
(-Dsrv)
See note
Specifies options with which you control your ODBC Driver and DataServer environment. See DataServer options and Using MS SQL Server and DataServer options for more information.
Note: When you specify a list of -Dsrv parameters, be sure not to include any spaces anywhere in this list.
Server Join
(-nojoinbysqldb)
Optional
Specifies that the client evaluates and performs queries that have joins. This might slow performance, but it provides results that are consistent with the query of an OpenEdge database.
Use -nojoinbysqldb at startup time.
If not specified, the server will perform joins, but results may not be consistent with identical joins run against an OpenEdge database.
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
* Using a remote DataServer configuration