OpenEdge Data Management: DataServer for Microsoft SQL Server

Connecting the DataServer
6–22
Table 6–8: Client DataServer Log entry types (2 of 2)
Log entry type Description
DS.Cursor Logs client-side cursor details. By default, setting the
DS.Cursor log entry type in the client context will
automatically set the Cursor log entry type in the server
context.
4GLTrans Logs client side transaction details. Level 4 of the entry type
writes client context information to the log file specific to
DataServers. Output from the 4GLTrans log entry type can
supplement output of the TRANS log entry type in the server
context.
For more detail on log entry types of the DataServer client context and other log entry types
specific to the client context, refer to OpenEdge Development: Debugging and
Troubleshooting.
Table 6–9 lists the server DataServer log entry types.
Table 6–9: Server Log entry types (1 of 2)
Log entry type Description
SQL Logs information about SQL queries. Similar to the legacy
qt_debug,SQL option.
• Level 2 (Basic) — Logs details of SQL query preparation
and execution.
• Level 3 (Verbose) — Adds bound values when prepared
and/or execute SQL utilize bind parameters.
Cursor Logs information about cursor details. Similar to the legacy
qt_debug,Cursor option.
• Level 2 (Basic) — Logs basic cursor details such as table
number, client and server cursor identifiers.
Trans Logs information about transaction details.
• Level 2 (Basic) — Logs messages when a SQL
transaction begins or ends on the server or when a
transaction is undone against the MS SQL Server
database.
• Level 3 (Verbose) — Adds messages for the beginning
and ending of sub-transactions and when it is undone.
• Level 4 (Extended) — Logs details about records locked
in a transaction including the type of lock, lock upgrades,
etc.