Hi
I was working on few sandboxes on a clover ETL server. I enabled SQL tracing and had to do that for each individual graph. I was wondering is there a way to enable SQL tracing at server level or in other words at global level as a property or something, instead of adding dbexecute components in individual graphs?
I was working on few sandboxes on a clover ETL server. I enabled SQL tracing and had to do that for each individual graph. I was wondering is there a way to enable SQL tracing at server level or in other words at global level as a property or something, instead of adding dbexecute components in individual graphs?
-
Hi
What i mean was DB tracing. The below link specifiy what i want to do.
http://www.orafaq.com/wiki/SQL_Trace
http://docs.oracle.com/cd/B10500_01/ser ... ltrace.htm
Basically i want to create .trc files, to trace the SQL query and track the efficiency of how DB is being accessed by ETL. I need this to analyze and improve performance of my pages. -
One way i was hoping to proceed here was to create a wrapper around the class invoked for initiating DB connection by clover ETL engine and update the trace session there.
Something like, before returning connection back to Clover, execute DB tracing queries. In this case for each sandbox or graph execution tracing will be enabled by default. We can again have a check like threadsafeconnection check to allow user to switch tracing on or off.
Is this a feasible solution?
Please sign in to leave a comment.
Comments 4