OpenEdge Data Management: DataServer for Microsoft SQL Server

Chapter 6: Connecting the DataServer
Note the following command used in a Windows client:
prowin32 mssholder -RO -db sports -dt MSS -ld mydemo -H host1
-S mssport -U bob -P bobpass -Dsrv qt_debug,EXTENDED
Note the following command used on a UNIX client:
pro mssholder -RO -db sports -dt MSS -ld mydemo -H host1
-S mssport -U bob -P bobpass -Dsrv qt_debug,EXTENDED
Unsupported connection parameters
You cannot use the following OpenEdge connection parameters when connecting to a
MS SQL Server database through the DataServer. If you do specify them, OpenEdge
and WebSpeed ignore them:
• Blocks in Database Buffers (-B)
• Before–image Filename (-g)
• Lock-table Entries (-L)
• Number of Users (-n)
• Buffered I/O—UNIX only (-r)
• Version 6 Query (-v6q)
• Raw I/O (-R)
Special connection issues
The DataServer (-Dsrv) parameter uses the PRGRS_CONNECT option to allow you to
pass ODBC-specific information to the ODBC driver. A DataServer connection string
contains all of the information needed to establish a connection. It consists of a series
of keywords/value pairs separated by semicolons. The DataServer for MS SQL Server
passes the connection string specified by the PRGRS_CONNECT option directly through
to the ODBC driver without modification. For more information and a complete list of
keywords, refer to the Microsoft ODBC programming reference documentation. The
parameter has the following syntax:
Syntax
-Dsrv PRGRS_CONNECT,connection-string;
ODBC-specific connection information is passed in connection–string. The
connection string is separated from the option by a comma (,) and ends with a
semicolon (;). There can be no spaces within connection-string. If any of the
name/value pairs does include a space, substitute the value &^ for the space.
224 OpenEdge Data Management: DataServer for Microsoft SQL Server