M
Marko Myllymäki
Guest
Background With database-request statement caching you can see, what a specific client is doing (= the stack trace of the last database-request statement) : http://knowledgebase.progress.com/articles/Article/P150383 This can be handy, for instance, for debugging purposes or just to find out, if a specific user is doing anything (maybe the user has just left the application running and left the office). Enhancement request We have an application where the client constantly polls the database (checks for new messages, verifies the session validity etc.) and then these polls are seen as database actions in the statement cache. So, these automatic polls prevent us to see, what the user is actually doing. We would like to filter out these polls which we are not interested in. The exclusion filtering could be done by table (do not use statement cache for the selected tables) or by program name (do not use statement cache in selected procedures). Either way would work in our case. It might also be useful to specify only the tables that we want to collect statement cache from (use statement cache only for the selected tables) but in our case the exclusion filter would be sufficient.
Continue reading...
Continue reading...
