I have an application that performs quite some sql statements to a client sql anywhere database and sometimes it's hard to figure out what exactly is happening and would like to do some tracing on DB level.
I've tried a few methods to log/trace sql statements but only with moderate or no success.
I've tried the following things.
I would have like to use application profiling since it looks really nice, but it starts up and doesnt seem to update. I can see my connections though (in application profiling), and when I perform some sql statements in my application I see that the amount of memory used by that connection/application changes.
PS: Other things I've tried. Using "The monitor": gives nothing away of sql commands using third party profilers in my application, but unfortunately these fail as well.
some help would be appreciated.
asked 02 Dec '13, 07:07
Use the two SQL commands to enable logging:
call sa_server_option ('Request_level_log_file', 'c:\\temp\\sql.log'); call sa_server_option ('Request_level_logging', 'SQL+hostvars')
you should find the sql commands in the created log file
call sa_server_option ('Request_level_logging', 'NONE')
answered 02 Dec '13, 11:02