Search This Blog

Saturday, May 9, 2009

SQL Monitor

By Erico Maish

The SQL Monitor enables you to see the actual statement calls made through SQL Links to a remote server or through the ODBC socket to an ODBC data source.

To open the SQL Monitor,
Choose Database|SQL Monitor.

You can elect to monitor different types of activity. Choose Options|Trace Options to bring up the Trace Options dialog box. This dialog allows you to select from different categories of activities to monitor. You can monitor any number of the following categories:

Prepared Query Statements:
Prepared statements to be sent to the server.

Executed Query Statements:
Statements to be executed by the server. Note that a single statement may be prepared once and executed several times with different parameter bindings.

Input Parameters:
Parameter data sent to servers when doing INSERTs or UPDATEs.

Fetched Data:
Data retrieved from servers.

Statement Operations:
Each operation performed such as ALLOCATE, PREPARE, EXECUTE, and FETCH

Connect / Disconnect:
Operations associated with connecting and disconnecting to databases, including allocation of connection handles, freeing connection handles, if required by server.

Transaction operations such as BEGIN, COMMIT, and ROLLBACK (ABORT).

Blob I/O:
Operations on Blob datatypes, including GET BLOB HANDLE, STORE BLOB, and so on.

Operations not covered by other categories.

Vendor Errors

Error messages returned by the server. The error message may include an error code, depending on the server.

Vendor Calls
Actual API function calls to the server. For example, ORLON for Oracle, ISC_ATTACH for InterBase.

The Buffer page of the Trace Options dialog allows you to specify how much trace information can be maintained in memory by the SQL monitor. You can choose to have all trace information maintained in a circular memory buffer, so that once the limit is reached, additional traces replace the first traces. Alternately, you may choose to write traces information to a disk file when the memory buffer becomes full.

More Here

No comments: