Kbase P130310: How can SQL transactions be monitored?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/9/2008 |
|
Status: Unverified
GOAL:
How can SQL transactions be monitored?
GOAL:
Is there a tool to monitor SQL transactions?
FACT(s) (Environment):
OpenEdge 10.x
Progress 9.x
FIX:
The transactions in SQL are managed by the TRANSACTION ISOLATION LEVEL selected for the user in the ODBC driver.
Any SQL-92 executable statement is executed as part of a transaction.
When you execute a statement and there is already an active transaction, the statement executes as part of the existing transaction.
If an active transaction does not exist, execution of the SQL statement starts a new transaction. This transaction becomes the active transaction and all subsequent SQL-92 statements will execute as part of this transaction until the application ends the transaction with an explicit COMMIT or ROLLBACK operation.
The COMMIT statement ends the currently active transaction. When a COMMIT statement is executed, all the changes made to the database by the transaction are made permanent.
The ROLLBACK statement undoes all the changes made to the database within the currently active transaction.
SQL transactions are just like transactions originating from ABL applications.
Promon utility can be used for the purpose of monitoring SQL and 4GL/ABL transaction.
In addition, as of OpenEdge 10.1B there is a SQL server side logging ability documented in the SQL Reference manual "SET PRO_SERVER LOG".
This gives very detailed information about what the server is doing for each connection.