Consultor Eletrônico

Status: Verified

GOAL:

DataServer startup, -Dsrv, parameters list by products

GOAL:

DataServer client session, -Dsrv, parameters list by products

FACT(s) (Environment):

Oracle DataServer
MS SQL DataServer
UNIX for Oracle DataServer
Progress 8.x for Oracle DataServer
Progress 9.1x for both Oracle and the MS SQL Server DataServer
Windows for both Oracle and MS SQL Server DataServer

FIX:

======================
DataServer for Oracle:
======================

qt_no_debug (This is a default parameter.)

qt_debug,EXTENDED (Prints additional information, such as cursor statistics.)

qt_debug,SQL (Prints SQL that the DataServer executes against the ORACLE DBMS.)

qt_debug,CURSOR (18835) (Information about the ORACLE cursors that the DataServer uses for internal ORACLE Call Interface (OCI) calls and for opening queries. It tracks when cursors open, close, and when the DataServer reuses them. It also summarizes each cursor's activity. These diagnostics are especially helpful when determining Progress and ORACLE maximum cursor settings or cursor "leaks" that your application might have.)

qt_debug,DATA-BIND (1029) (Information about the data types, buffer sizes, and addresses that the DataServer and ORACLE use when binding variables.)

qt_debug,PERFORMANCE (55775) (Information on the time certain operations take. These statistics are available only for some platforms. Note that any time differences between what the DataServer reports and what the ORACLE tkprof utility reports might be due to network performance issues, rather than to DataServer or ORACLE behavior.)

qt_debug,SUMMARY (1073797455) (Information on cursors and timing in summary form as a Progress data (.d) file. Call Progress Software Corporation Consulting for assistance with this file. This option is not available as a QUERY-TUNING phrase option.)

qt_no_separate_connection Specify whether each cursor should use a separate connection to the MS SQL Server database. The default is qt_no_separate_connection, which provides behavior that is consistent with an OpenEdge database. Specify qt_separate_connection to use a separate connection. Executing cursors in separate connections can improve performance because the DataServer does not have to restart the cursors.

qt_debug,VERBOSE (122879) (Information on all of the above. This option generates a very large log file. Remember to clear your log file before using this option to test a procedure.)

NOTE: The numeric number corresponds to the parameter switch. You can either use the switch name or number.

qt_cache_size,<integer value in bytes or # of ROW> (In bytes, 1024 minimum and maximum 65535; in row, 1 for single table and 2 for a join)

-nojoinbysqldb (The client performs the join. The default is JOIN-BY-SQLDB. Does not override the explicit use of JOIN-BY-SQLDB in the QUERY-TUNING phrase)

qt_no_bind_where (Specifies whether the DataServer uses ORACLE bind variables for values in WHERE clauses. Specify qt_no_bind_where to use literals. Used at run time only. The default is qt_bind_where)

qt_lookahead (Specifies whether the DataServer uses lookahead or standard cursors. Specify qt_no_lookahead for behavior that is consistent with Progress.
Default is qt_lookahead, except with statements that use an EXCLUSIVE lock)

skip_schema_check

CAUTION: If you use the skip schema check option, the DataServer skips the schema check and does not detect discrepancies between the schema definitions and the data definitions. If there are discrepancies and the DataServer continues to process queries, inserts, and deletions, your data may become corrupted. Progress Software Corporation recommends that you weigh carefully the performance benefit against the risk to your database before deciding to use -Dsrv skip_schema_check.

====================================
DataServer For Microsoft SQL Server:
====================================

qt_no_debug (This is a default parameter)

qt_debug,EXTENDED (Prints additional information, such as cursor statistics)

qt_debug,SQL (Prints SQL that the DataServer executes against the ORACLE DBMS)

qt_cache_size,<integer value in bytes or # of ROW> (In bytes, 1024 minimum and maximum 65535; in row, 1 for single table and 2 for. a join)

-nojoinbysqldb (The client performs the join. The default is JOIN-BY-SQLDB. Does not override the explicit use of JOIN-BY-SQLDB in the QUERY-TUNING phrase)

qt_lookahead (Specifies whether the DataServer uses lookahead or standard cursors. Specify qt_no_lookahead for behavior that is consistent with Progress.
Default is qt_lookahead, only when statements use NO-LOCK)

PRGRS_IDBUF,<numeric value such as 100> (Specifies the number of keys in the scrolling buffer. The value must be greater than 0. The default value is 25 keys. This parameter applies to all nonlookahead cursors. )

PRGRS_MINBUF,<numeric value such as 10000> (Specifies the minimum size of the buffer used to get data from the DataServer. Use this keyword only with drivers that fail to fetch large records. The default value is 500 bytes. If you specify a value smaller than the default, Progress uses the default value.)

MAX_ROWS,<numeric value such as 10000> (Specifies the maximum number rows to be return to progress application by the ODBC driver.)

Progress-supplied Option ------ ODBC-defined Option

ACCESS_MODE --------------------- SQL_ACCESS_MODE
ASYNC_ENABLE --------------------- SQL_ASYNC_ENABLE
AUTOCOMMIT ---------------------- SQL_AUTOCOMMIT
LOGIN_TIMEOUT -------------------- SQL_AUTOCOMMIT
MAX_LENGTH ---------------------- SQL_MAX_LENGTH
MAX_ROWS ------------------------ SQL_MAX_ROWS
NOSCAN --------------------------- SQL_NOSCAN
OPT_TRACE ----------------------- SQL_OPT_TRACE
QUERY_TIMEOUT -------------------- SQL_QUERY_TIMEOUT
TXN_ISOLATION ------------------- SQL_TXN_ISOLATION

NOTE: Refer to an ODBC application developer's guide for information on the ODBC-defined options.

When you specify a Progress-supplied ODBC option with the -Dsrv startup parameter, the DataServer sends the option to the ODBC dri