We're creating the hash within DPA based on output from the RDBMS. For example, we'll create the hash in SQL Server from parts of the sql_handle, and some other factors. For Oracle, we actually get the hash from Oracle itself.
Thus the problem - if the RDBMS sees it as a new query, so do we.
Recommendation: You can create a report that will look for specific SQLtext (some identifying pattern) that will pull back all of the hashes that match that pattern.
Now, to actually change the hash in the repo would not be recommended as there are a LOT of dependencies that don't necessarily follow RI (think summary tables, dimensions, plans, etc.).
I think you may be limited by the report for pulling like SQL...
Anyone else have any ideas?
I don't know of a way to do what @awickham10 is asking for with the current version of DPA.
I want a feature that will enable me to group hashes. So if a statement is non-parameterized or a statement in a procedure changes, I could link the old and new versions together so I could see the performance change in the chart by the length of one bar changing. And/or I could link the hashes for one stored procedure together to track performance of the procedure as a whole instead of individual statements. However, I envision setting up and maintaining those groups to be a manual process.
Adding a feature to automatically group hashes based on a pattern would be good enhancement to that. Here are some related feature suggestions that people could vote for and/or comment on:
Ability to group or give query's the same name (this is the most relevant one, but has very few votes at the moment)