OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Connecting the <strong>Data</strong><strong>Server</strong><br />
Connection guidelines<br />
6–8<br />
When you create a schema holder, you specify certain connection in<strong>for</strong>mation, such as the<br />
physical and logical names <strong>for</strong> your MS <strong>SQL</strong> <strong>Server</strong> database and the user and password<br />
in<strong>for</strong>mation. <strong>OpenEdge</strong> stores this in<strong>for</strong>mation so that you do not have to provide it each time<br />
you connect. After you consider your security requirements, proceed to connect the schema<br />
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 levels of<br />
security:<br />
• Standard — Requires that a client pass a user ID and password that the MS <strong>SQL</strong> <strong>Server</strong><br />
database validates against the list of users in the syslogins table. The request typically<br />
comes from a nontrusted connection, such as through TCP/IP. The <strong>OpenEdge</strong> client or<br />
WebSpeed agent passes this in<strong>for</strong>mation with the User ID (-U) and Password (-P)<br />
connection parameters.<br />
• Integrated — Relies on the Windows operating system to validate user in<strong>for</strong>mation. The<br />
MS <strong>SQL</strong> <strong>Server</strong> database accepts user in<strong>for</strong>mation from the process that requests a<br />
connection. The request must come from a trusted connection, such as one using Named<br />
Pipes. The MS <strong>SQL</strong> <strong>Server</strong> database 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 consists<br />
entirely of spaces, or a user ID that matches the user that started the process, the MS<br />
<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 and<br />
password.<br />
Progress Software Corporation recommends the following guidelines <strong>for</strong> working with a MS<br />
<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 using<br />
remote <strong>OpenEdge</strong> clients.<br />
• If you are using mixed security, always have the clients specify the -U and -P connection<br />
parameters.
Change language