| Title: | SQL/Services Forum |
| Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) |
| Moderator: | SQLSRV::MAVRIS |
| Created: | Thu Oct 13 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2214 |
| Total number of notes: | 8586 |
CT using 7.0-00 Rdb and SQS.
Do we have any server side solution that would allow us to monitor the
SQL being executed via a SQL/Services executor?
I know I can trace the BLR, but that is not really an ideal solution.
Is there a server side trace option I have missed?
Colin - Danmark
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2166.1 | Define SQLSRV$SERVER_LOG to client log value | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Fri Mar 14 1997 13:21 | 17 |
Hi Colin, Sure, we do provide executor protocol logging. Note that this is an internal tool with no guarantees attached. We believe it works correctly in SQL/Services 7.0, but this is the logging that used to cause the executor to ACCVIO in earlier versions. To enable logging, define SQLSRV$SERVER_LOG to the logging level you want. This should either be a system logical to enable logging for all services, or a logical defined in a process initialization file for a specific service. SQLSRV.H specifies the client logging values. These also apply to executor logging. Just add up the options you want and define SQLSRV$SERVER_LOG to this value. In order to see the SQL statements being executed by SQL/Services, be sure to specify SQLSRV_LOG_PROTOCOL (4). Sue | |||||
| 2166.2 | FYI - protocol level logging only in executor | ORASQS::OXBURY | Oracle Corporation, Rdb Desktop Group|DTN 381-2704 | Mon Mar 17 1997 08:50 | 4 |
Just a quick note - the executor really only supports protocol level
logging - it doesn't support routine (statement) level logging.
Si
| |||||