| 3 |
|
IntegratedMonitoring |
| 4 |
|
==================== |
| 5 |
|
|
| 6 |
< |
This is a minor change to the Employee example and adds a second Monitor Form to record a selected set of SQL events in a TMemo journal. The events monitored can be changed by changing the trace options in the TIBDatabase. |
| 6 |
> |
This is a minor change to the Employee example and adds a second "Monitor Form" |
| 7 |
> |
to record a selected set of SQL events in a TMemo journal. The events monitored can |
| 8 |
> |
be changed by changing the trace options in the TIBDatabase. |
| 9 |
|
|
| 8 |
– |
Windows users should note the need for a trip round the message loop on the monitor form to ensure that all events are correctly displayed. |
| 10 |
|
|
| 11 |
|
Remote Monitoring |
| 12 |
|
================= |
| 13 |
|
|
| 14 |
< |
This example show how TISQLMonitor can be used to monitor another application. This application comprises one form containg a single TMemo used to record the SQL event journal. Run it at the same time as IntegratedMonitoring and you will see the SQL event journal. Note that what is monitored is controlled from the IntegratedMonitoring application which sets the monitored events in its trace flags and must call "EnableMonitoring" for any monitoring to take place. |
| 14 |
> |
This example show how TISQLMonitor can be used to monitor another application. |
| 15 |
> |
This application comprises one form containing a single TMemo used to record the |
| 16 |
> |
SQL event journal. Run it at the same time as IntegratedMonitoring and you will |
| 17 |
> |
see the SQL event journal here as well. Note that what is monitored is controlled |
| 18 |
> |
from the IntegratedMonitoring application which sets the monitored events |
| 19 |
> |
in its trace flags and must call "EnableMonitoring" for any monitoring to |
| 20 |
> |
take place. |
