We have a situation where the application accessing the database generates SQL Queries on the fly, but for some reason it aliases the field names with different numbers depending on the Application Server that runs the query. Is there any way to force DPA to join the multiple queries so that the statistics for the query sum up properly and give us a real picture of how poor the query is performing?
You might be able to do a custom report for now. If you know the hash values you are after using these custom reports. Changing the query some to group by more then one hash value. Note the top one would be for a SQL server repository and the second an Oracle repository. Just a thought for getting the data on this from DPA as it is now.
The issue we run into is that the database engine itself will assign a different sql_handle or sql_id if anything in the query changes. Really the only way to bridge this is to name the hashes as discovered with similar naming conventions so you can easily recognize when queries are related. How to recognize and do this programmatically might be subject to misses or false positives - yet an interesting problem to ponder!
Thanks for the information. This is what I expected. It would seem that custom reports is likely the best way to try and get the summation of the various queries the Application ORM is randomly generating.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.