13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Direct Connect<br />

(-DirectConnect)<br />

Password<br />

(-P)<br />

Single–User Mode<br />

(-1)<br />

Read-Only<br />

(-RO)<br />

Optional. For use<br />

with Progress<br />

Explorer<br />

connections<br />

You can create a parameter file <strong>for</strong> each database:<br />

Connecting a schema holder<br />

Table 6–1: <strong>Data</strong><strong>Server</strong> connection parameters (2 of 2)<br />

Local Cache<br />

(-cache)<br />

<strong>Data</strong><strong>Server</strong><br />

(-Dsrv)<br />

Parameter Status Description<br />

<strong>Server</strong> Join<br />

(-nojoinbysqldb)<br />

Instructs the client to bypass the controlling Name<strong>Server</strong><br />

and connect directly to the MS <strong>SQL</strong> <strong>Server</strong> <strong>Data</strong><strong>Server</strong><br />

Broker.<br />

If not specified, the connection is made through the<br />

Name<strong>Server</strong>.<br />

Required Supplies the password that the <strong>Data</strong><strong>Server</strong> uses to log into<br />

the MS <strong>SQL</strong> <strong>Server</strong> database. Different login name and<br />

password combinations allow <strong>for</strong> different levels of user<br />

privileges.<br />

Optional Specifies that a schema holder is used in single-user mode.<br />

Single–User Mode is the default unless a server is started<br />

<strong>for</strong> the schema holder.<br />

If not specified, -RO or remote connection parameters are<br />

required.<br />

Optional Specifies that a schema holder is read-only. Connecting a<br />

schema holder as read-only increases processing speed at<br />

client startup time. It also allows multiple client processes<br />

on the same machine to access the schema holder without<br />

starting additional server processes.<br />

If not specified, the database is opened <strong>for</strong> update as well<br />

as read access.<br />

Optional Specifies that you are using a local cache file <strong>for</strong> the<br />

schema holder. Create the cache file with the SAVE CACHE<br />

COMPLETE statement.<br />

If not specified, no cache file is used.<br />

See note Specifies options with which you control your ODBC<br />

Driver and <strong>Data</strong><strong>Server</strong> environment. See the “<strong>Data</strong><strong>Server</strong><br />

options” section on page 8–4 and the “Using MS <strong>SQL</strong><br />

<strong>Server</strong> and <strong>Data</strong><strong>Server</strong> options” section on page 8–6 <strong>for</strong><br />

more in<strong>for</strong>mation.<br />

Note: When you specify a list of -Dsrv parameters, be<br />

sure not to include any spaces anywhere in this list.<br />

Optional Specifies that the client evaluates and per<strong>for</strong>ms queries that<br />

have joins. This might slow per<strong>for</strong>mance, but it provides<br />

results that are consistent with the query of an <strong>OpenEdge</strong><br />

database.<br />

Use -nojoinbysqldb at startup time.<br />

If not specified, the server will per<strong>for</strong>m joins, but results<br />

may not be consistent with identical joins run against an<br />

<strong>OpenEdge</strong> database.<br />

• For a local <strong>Data</strong><strong>Server</strong>, the parameter file must contain the -db parameter and can<br />

optionally contain the -Dsrv, -U, and -P connection parameters, depending on the<br />

requirements of the data service.<br />

6–11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!