13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Connecting the <strong>Data</strong><strong>Server</strong><br />

6–26<br />

Syntax<br />

ds__.lg.<br />

Enabling ABL-to-<strong>SQL</strong> Correlation in Logging<br />

The Enhanced Logger allows ABL-to-<strong>SQL</strong> correlation so you can compare ABL database<br />

requests with <strong>SQL</strong> directives that are executed on the server. In the <strong>Data</strong><strong>Server</strong><br />

In the <strong>Data</strong><strong>Server</strong> log file, ABL-to-<strong>SQL</strong> correlation includes in<strong>for</strong>mation from the client<br />

context, the ABL procedure name and line number, along with the server context <strong>SQL</strong> that was<br />

generated based on the ABL code and run against the <strong>for</strong>eign data source. The correlation is<br />

enabled using the -Dsrv PRGRS_LOG_ABL,n switch where n ranges from 0 to 2, as demonstrated<br />

in the following example:<br />

-Dsrv logentrytypes,<strong>SQL</strong>,PRGRS_LOG_ABL,1<br />

Table 6–12 describes the PRGRS_LOG_ABL connect option values:<br />

Table 6–12: PRGRS_LOG_ABL connect option values<br />

Option Value Description<br />

0 Disables the ABL to <strong>SQL</strong> correlation feature. No correlation<br />

in<strong>for</strong>mation will be logged.<br />

1 Enables the ABL to <strong>SQL</strong> correlation feature <strong>for</strong> <strong>SQL</strong>-related log<br />

entry types. Every <strong>SQL</strong> request derived from the log entry type<br />

output is preceded by ABL filename and line number which can be<br />

correlated to a compiled listings file.<br />

2 Enables a superset of value 1 which, along with correlation<br />

in<strong>for</strong>mation, includes visual delimiters marking the start and end of<br />

each ABL file module.<br />

Note: The <strong>SQL</strong> log entry type is specifically designed to output <strong>SQL</strong>-related logging<br />

in<strong>for</strong>mation and there<strong>for</strong>e would be used most commonly in conjunction with the<br />

PRGRS_LOG_ABL -Dsrv switch. However, the PRGRS_LOG_ABL switch can be enabled<br />

to acquire module and line number in<strong>for</strong>mation with any log entry type that writes <strong>SQL</strong><br />

request in<strong>for</strong>mation to the log.<br />

Local schema caching<br />

By using a local file to store schema definitions, you can access them more quickly. Running<br />

<strong>Data</strong><strong>Server</strong> applications with a local schema cache can result in better per<strong>for</strong>mance in<br />

networked environments.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!