Progress
DataServer for
Microsoft SQL Server
Guide


Connecting a Schema Holder at Startup

Progress supports connection parameters that you can use to connect both the Progress schema holder and a 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.

Table 4–1 describes the database connection parameters that you use when you connect to a schema holder and a SQL Server™ database through the DataServer.

Table 4–1: DataServer Connection Parameters
Parameter
Status
Description
Database Type MSS
(-dt MSS)
Optional
Specifies that the type of the target data source is MSS (MicroSoft® SQL Server™).
Physical Database Name
(-db)
Required
Indicates the name by which Progress recognizes the 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 SQL Server™ database.
Logical Database Name
(-ld)
Optional
Specifies the logical name of the 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 SQL Server™ demo database as mydemo. In this case, the physical name is demo, and the logical name is mydemo.
Host Name
(-H)
Required for remote DataServer
Indicates the name of the NT 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 Progress Explorer, specify the service name or IP address of the host machine where the NameServer resides. If you are using probrkr, ProControl, or the Progress Explorer without a NameServer, specify the service name or IP address of the host machine where the broker resides.
Network Type
(-N )
Optional
Indicates the network type. TCP is the only possible value.
User ID
(-U)
Required
Supplies the login name that the DataServer uses to log into the SQL Server™ database.
Explorer Redirection
(-SVUB)
Required for Progress Explorer connections
Redirects connection logic to the Progress Explorer instead of probrkr or ProControl. For more information see the "Starting and Stopping a Broker Process from the Progress Explorer and Connecting a Client" section.
Data Service
(-DataService)
Required for Progress Explorer connections
Specifies the data service the NameServer uses. For more information, see the "Starting and Stopping a Broker Process from the Progress Explorer and Connecting a Client" section.
Password
(-P)
Required
Supplies the password that the DataServer uses to log into the 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.
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.
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.
DataServer
(-Dsrv)
See note
Specifies options with which you control your ODBC Driver and DataServer environment. See the "Query Tuning with Connection and Startup Parameters" section 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 Progress behavior.
Use -nojoinbysqldb at compile time. It has no effect at run time.

You can create a parameter file for each database:

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 the Progress Startup Command and Parameter Reference.

Using a Local DataServer Configuration: Examples

Use the following general command syntax to start Progress:

You can type these commands on the command line of a program item property box.

The following examples start Progress in a local DataServer configuration. In these examples:

Using a Remote DataServer Configuration: Examples

This configuration is available only with the Enterprise DataServer for SQL Server™.

Use the following command syntax to start Progress:

On a Windows Client:

prowin32 schema-holder-name -1 -db datasrc-name -dt MSS
  -ld logical-datasrc-name -H hostname -S service-name
  -N TCP -U userID -P password -Dsrv
  qt_debug,EXTENDED 

On a UNIX Client:

pro schema-holder-name -db datasrc-name -dt MSS
  -ld logical-datasrc-name -H hostname -S service-name
  -N TCP -U userID -P password -Dsrv
  qt_debug,EXTENDED 

The following examples start Progress in a remote DataServer configuration. In these examples:

On a Windows Client:

prowin32 mssholder -RO -db sports -dt MSS -ld mydemo -H host1
-S mssport -N TCP -U bob -P bobpass
-Dsrv qt_debug,EXTENDED 

On a UNIX Client:

pro mssholder -RO -db sports -dt MSS -ld mydemo -H host1
-S mssport -N TCP -U bob -P bobpass
-Dsrv qt_debug,EXTENDED 


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