OracleMonitor

jabarreras

Member²
When you are testing your forms you must write in the uses clause OracleMonitor if you want to 'sniff' sql sentences your sending to the Server. It is really useful. But when the application is in a production environment, Do this forms with OracleMonitor produce more load of work (at client side) than not using OracleMonitor?
 
For each database access function, the application will check if the Oracle Monitor is running by investigating some global shared memory. For the average application, the performance consequences will be negligible.

If you have a lot of batch oriented local database access, it may be useful to remove the OracleMonitor unit before deploying your application.

------------------
Marco Kalter
Allround Automations
 
Back
Top