OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Connecting a schema holder<br />
Connecting a schema holder<br />
As described previously, connection can take place automatically using the in<strong>for</strong>mation that you<br />
enter when you create a schema holder. In addition, <strong>OpenEdge</strong> provides the following<br />
techniques <strong>for</strong> connecting to a schema holder:<br />
• Use the <strong>Data</strong> Dictionary or <strong>Data</strong> Administration. From the main menu, select <strong>Data</strong>base→<br />
Connect and supply the schema holder’s physical name and the appropriate connection<br />
parameters. You can then select your MS <strong>SQL</strong> <strong>Server</strong> database as your working database<br />
and connect to it. You cannot use the Utilities→ Edit <strong>OpenEdge</strong> Auto–Connect option<br />
to connect to a MS <strong>SQL</strong> <strong>Server</strong> data source.<br />
• Use the ABL CONNECT statement (see its reference entry in <strong>OpenEdge</strong> Development: ABL<br />
Reference). A CONNECT statement must first list the schema holder and related connection<br />
parameters, then the MS <strong>SQL</strong> <strong>Server</strong> database and related parameters.<br />
This command connects a schema holder named mssholder and MS <strong>SQL</strong> <strong>Server</strong> database<br />
named mssdemo:<br />
CONNECT mssholder -1 -db mssdemo -dt MSS<br />
-Dsrv qt_debug,EXTENDED<br />
• Use connection parameters when you start <strong>OpenEdge</strong>. You can include these parameters<br />
on the program item command line or in a parameter file that you specify when you start<br />
<strong>OpenEdge</strong>. A parameter file is portable and easy to maintain. For in<strong>for</strong>mation on creating<br />
a parameter file, see <strong>OpenEdge</strong> Deployment: Startup Command and Parameter Reference.<br />
You can use combinations of different connection techniques. For example, you can connect the<br />
schema holder at startup, then connect to the <strong>Data</strong><strong>Server</strong> using the <strong>OpenEdge</strong> CONNECT<br />
statement. If the proper connect in<strong>for</strong>mation is stored in the schema holder, referencing a table<br />
in the MS <strong>SQL</strong> <strong>Server</strong> database will cause the <strong>Data</strong><strong>Server</strong> to issue the connect statement<br />
automatically. Any combination of connection techniques works, as long as you first connect to<br />
the schema holder and then the MS <strong>SQL</strong> <strong>Server</strong> data source.<br />
If you are not updating the schema holder, you can specify the Read-only (-RO) connection<br />
parameter to enhance <strong>Data</strong><strong>Server</strong> per<strong>for</strong>mance.<br />
If you connect to the schema holder and the MS <strong>SQL</strong> <strong>Server</strong> database in a single startup<br />
command or connection statement, be sure to specify parameters that affect the schema holder<br />
be<strong>for</strong>e the <strong>Data</strong>base Name (-db) parameter. Specify only those parameters that affect the MS<br />
<strong>SQL</strong> <strong>Server</strong> database connection after the -db parameter.<br />
The following section explains how to connect both a schema holder and a MS <strong>SQL</strong> <strong>Server</strong><br />
database when you start up <strong>OpenEdge</strong>.<br />
Connecting a schema holder at startup<br />
<strong>OpenEdge</strong> supports connection parameters that you can use to connect both the <strong>OpenEdge</strong><br />
schema holder and a MS <strong>SQL</strong> <strong>Server</strong> database at startup. These parameters control how your<br />
system connects to a database. If the <strong>Data</strong><strong>Server</strong> runs in a remote configuration, your startup<br />
command or parameter file always includes parameters that control networking options.<br />
6–9