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.

Connection guidelines<br />

Connection guidelines<br />

When you create a schema holder, you specify certain connection in<strong>for</strong>mation, such as<br />

the physical and logical names <strong>for</strong> your MS <strong>SQL</strong> <strong>Server</strong> database and the user and<br />

password in<strong>for</strong>mation. <strong>OpenEdge</strong> stores this in<strong>for</strong>mation so that you do not have to<br />

provide it each time you connect. After you consider your security requirements,<br />

proceed to connect the schema holder and then the data source.<br />

Connections and security in Windows<br />

When you configure an ODBC data source in Windows, you can choose one of three<br />

levels of security:<br />

• Standard — Requires that a client pass a user ID and password that the MS <strong>SQL</strong><br />

<strong>Server</strong> database validates against the list of users in the syslogins table. The<br />

request typically comes from a nontrusted connection, such as through TCP/IP.<br />

The <strong>OpenEdge</strong> client or WebSpeed agent passes this in<strong>for</strong>mation with the User<br />

ID (-U) and Password (-P) connection parameters.<br />

• Integrated — Relies on the Windows operating system to validate user<br />

in<strong>for</strong>mation. The MS <strong>SQL</strong> <strong>Server</strong> database accepts user in<strong>for</strong>mation from the<br />

process that requests a connection. The request must come from a trusted<br />

connection, such as one using Named Pipes. The MS <strong>SQL</strong> <strong>Server</strong> database<br />

per<strong>for</strong>ms no additional validation.<br />

• Mixed — Accepts requests from trusted or nontrusted connections:<br />

– If the connection is trusted and the client provides no user ID, a user ID that<br />

consists entirely of spaces, or a user ID that matches the user that started the<br />

process, the MS <strong>SQL</strong> <strong>Server</strong> database accepts the connection.<br />

– If the connection is nontrusted, the <strong>OpenEdge</strong> client must provide the user ID<br />

and password.<br />

Progress Software Corporation recommends the following guidelines <strong>for</strong> working with<br />

a MS <strong>SQL</strong> <strong>Server</strong> database and Windows security:<br />

• Configure a MS <strong>SQL</strong> <strong>Server</strong> database to use standard or mixed security if you are<br />

using remote <strong>OpenEdge</strong> clients.<br />

• If you are using mixed security, always have the clients specify the -U and -P<br />

connection parameters.<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> 217

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

Saved successfully!

Ooh no, something went wrong!