Devart Forums

Hi,

I'm developing a multitier app (I use RemObjects DA) and for access to DB I use UniDAC (Oracle database).

I need to log the SQL generated from the server app I wolud use the TUniSQLMonitor component to capture and log all.

In the server project I have a main datamodule and many services which are instantiated by threads. In order to link the session data to the log, I would need to insert the TUniSQLMonitor component in each service instead of centralizing the log in a single point. So I will insert as many TUniSQLMonitor components as there are services. This can be a problem?

For this I have disabled all options (moDialog, moSQLMonitor, moDBMonitor, miCustom and moHandled) and I use only the event OnSQL.

Thank you very much

You can use a single TUniSQLMonitor component in your server app, since this component can work with multiple connections and log the generated SQL for each of them. Feel free to contact us if you have any further questions.

Hi MaximG

thank you very much for your answer.

I had already analyzed that with only one UniSQLMonitor component I can log everything. The problem, however, is that I need to log information that is specific to the service and link these information to the SQL statments that I manage to capture with the OnGetSQL event of the UniSQLMonitor component.

I don't need an integration with DBMonitor because I use an advanced log system that displays a lot of other information.

I need to insert a TUniSQLMonitor component on each service exposed by my application server. Having many instances of UniSQLMonitor (I have disabled all options) can I have any problems?

Thank you very much

We cannot make any assumptions about success or failure of this approach to logging individual services without hands-on experience with it. You may try to create a sample project to see how it works out for you.