|
I have a web application that runs on Sybase 12 using PowerDynamo (gasp). Every once in a while I will see the webserver pinning and I think there may be a query running that is returning a huge amount of rows and the webserver is processing all those rows. My question is - is it possible to see the actual sql queries (cursors) that are open and executing? The ideal scenario would be to be able to examine the sql of the open queries and find out which one is the culprit. My only remedy right now is to reset IIS and then everything is back to normal (for a while). Thanks for any insight on this! |
|
There are two approaches to addressing this. One is the older Request Logging feature. The other is Diagnostic Tracing, aka tracing. Both fall into the category of Performance monitoring and diagnostic tools and each have their benefits and purpose. Tracing is available as a GUI Wizard feature of Sybase Central; as a property/attribute of the database you are interested in. Request logging can be enabled as an attribute of the server and can be filtered on a specific connection or database or server wide. I've been using request logging for years (across many versions) but you do need to visually parse a log format that is not well documented but it has the advantage you can browse it with an editor while the request is running . . . Tracing tends to be more useful capturing a period of time and analysis requests that have completed running (to see which runs run poorly and to visualize workloads, etc . . .) I hope this helps a little. |
