Similar to access logs, another useful type of logging, especially when debugging an issue, is SQL logging. In this recipe, we will see how to turn on SQL logging.
Similar to access logs, SQL logging is also turned ON from the user interface at Administration | System | Troubleshooting and Support | Logging & Profiling.
Just as with access logs, the changes are temporary and will revert back in the next restart. Permanent changes can be made in the WEB-INF/classes/log4j.properties
file, although this is not recommended because SQL access logs can take up a large amount of space and may adversely affect performance.
In such an event, the logging entry to be modified is as follows:
##################################################### # SQL logs ##################################################### # # Beware of turning this log level on. At INFO level it will log every SQL statement # and at DEBUG level it will also log the calling stack trace....