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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Changing connection in<strong>for</strong>mation in a schema holder<br />

Changing connection in<strong>for</strong>mation in a schema holder<br />

The Edit Connection In<strong>for</strong>mation utility allows you to change a MS <strong>SQL</strong> <strong>Server</strong><br />

database’s connection in<strong>for</strong>mation or logical name in the associated schema.<br />

To change connection in<strong>for</strong>mation <strong>for</strong> a schema holder from the <strong>Data</strong><br />

Administration tool:<br />

1. Access the <strong>Data</strong> Administration, if you are not already there, and select<br />

<strong>Data</strong><strong>Server</strong>→ MSS <strong>SQL</strong> <strong>Server</strong> Utilities→ Edit Connection In<strong>for</strong>mation. The<br />

following dialog box appears:<br />

2. Make changes to the Connection Parameters fields as required. When you are<br />

done, choose OK to return to the <strong>Data</strong> Administration main window.<br />

The changes do not take effect until you disconnect and reconnect the schema holder.<br />

When you reconnect, <strong>OpenEdge</strong> uses the new connection parameters.<br />

For details on connection parameters, see Chapter 6, “Connecting the <strong>Data</strong><strong>Server</strong>,”<br />

and <strong>OpenEdge</strong> Deployment: Startup Command and Parameter Reference.<br />

Note: If you change the ODBC <strong>Data</strong> Source Name (DSN), do not select a DSN that<br />

uses a different ODBC driver than the original DSN. Configuration switches<br />

residing in the schema holder are dependent on the driver name. You will<br />

receive only a warning if you use a different driver, but the schema holder<br />

configuration may no longer match the characteristics of the driver and could<br />

cause unpredictable run-time results.<br />

<strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong> 275

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

Saved successfully!

Ooh no, something went wrong!