OpenEdge Data Management: DataServer for Microsoft SQL Server

Connecting a schema holder
Table 6–3 describes the query-tuning options that you can specify with the -Dsrv parameter.
Table 6–3: Connection query-tuning options
qt_no_debug
qt_debug,SQL
qt_debug,EXTENDED
qt_debug,CURSOR
Option Description
qt_debug,PERFORMANCE
qt_debug,CALL_SUMMARY
qt_debug,VERBOSE
qt_lookahead
qt_no_lookahead
qt_separate_connection
qt_no_separate_connection
Specifies whether the DataServer prints debugging information that it
generates for the query to the dataserv.lg file. The default is qt_no_debug,
to supply no debugging information. To override the default, specify
qt_debug,option as follows:
• Specify qt_debug,SQL to record the SQL sent to the ODBC driver in
the dataserv.lg file. Note that this SQL contains place holders for
values which will be bound to the statement when sent to the data
source
• Specify qt_debug,EXTENDED to print information such as cursor
statistics in addition to the SQL statements executed by the DataServer
• Specify qt_debug,CURSOR to print information about the cursors that
the DataServer uses for internal calls and for opening queries
• Specify qt_debug,PERFORMANCE to print information on the amount of
time that certain operations take
• Specify qt_debug,CALL_SUMMARY to print information on cursors and
timing
• Specify qt_debug,VERBOSE to print all of the information gathered by
the other qt_debug options
For more detailed descriptions of these options, see the Appendix D, “Using
qt_debug to Analyze Performance.” For information on Enhanced Logger
options that replace the qt_debug options, see “Analyzing performance with
the Enhanced Logger” section on page 6–18.
Specifies whether the DataServer uses lookahead or standard cursors. To
generate efficient queries, qt_lookahead is the default in the following
cases:
• Statements that use NO-LOCK
• Statements that use SHARE-LOCK with transaction isolation level set to
read uncommitted
Specify qt_no_lookahead for query behavior that is consistent with an
OpenEdge database.
Specifies 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_cache_size,integer Specifies the size in bytes of the cache used by lookahead cursors. A larger
cache size can improve performance for queries that return a large number
of records because the DataServer might need fewer SQL statements to get
the results.
Minimum: The DataServer always caches at least one record.
Maximum: None
Default: 10,000 when block cursors are enabled (the default). 30,000 when
block cursors are disabled.
6–17