OpenEdge Data Management: DataServer for Microsoft SQL Server

Connecting the DataServer
6–18
The following example shows how to use the query-tuning options to enhance performance.
The DataServer opens a separate connection to MSS (Microsoft SQL Server) for each cursor
and writes an extended report on the SQL statements it executes, as shown:
CONNECT holder -db infdb -dt MSS -ld demo -U user -P password -Dsrv
qt_separate_connection,qt_debug,EXTENDED.
OpenEdge provides a startup parameter called Server Join (-nojoinbysqldb) that controls the
default JOIN–BY–SQLDB behavior. You specify this parameter in the startup command for your
OpenEdge session. It overrides the JOIN–BY–SQLDB default so that the client evaluates and
performs joins. Using this parameter might slow performance, but it provides results that are
consistent with queries run against an OpenEdge database. See Chapter 2, “Initial Programming
Considerations,” for more information.
Analyzing performance with the Enhanced Logger
The Enhanced Logger infrastructure provides a means for either standard reporting of run-time
activity or logging diagnostic data for troubleshooting problems based on a set of logging
characteristics. The DataServer can be enabled to write information to a log file. You control
the type and amount of information logged using a combination of log entry types and logging
levels. Log entry types are categories of information written to the log file. Logging levels
control the amount of logging information for any given log entry type.
The legacy qt_debug logging infrastructure only logged server information but the Enhanced
Logger framework for DataServers offers two logging contexts:
• Server context for Server-specific log entries
• Client context, which shares logging information with OpenEdge clients and AppServer
agents.
LOG-MANAGER system handle attributes and methods
The LOG-MANAGER system handle controls logging settings for the OpenEdge client and
DataServer client contexts. The LOG-MANAGER attributes and methods allow you to
programmatically control the logging levels and log entry types during the execution of your
program.
Table 6–4 lists the function of each LOG-MANAGER system handle attribute.
Table 6–4: LOG-MANAGER system handle attributes (1 of 2)
Attribute Access Function
ENTRY-TYPES-LIST Readable Returns a list of all valid entry types.
LOG-ENTRY-TYPES Readable/Writable Returns a list of one or more types of log
entries.
LOGFILE-NAME Readable/Writable Returns the name of the log file.
LOGGING-LEVEL Readable/Writable Returns the level at which log entries are
written.