Please consider allowing individual database servers or individual clients to be flagged as needing to compare full SQL contents (including any comments) when determining SQL uniqueness.
Currently DPA appears to ignore contextual comments inserted into SQL queries and evaluates the core query.
Consequently, If a query comment changes but not the core sql, the captured SQL text is not updated.
(There is also no direct way to force SQL text to be recaptured without running SQL against the DPA repository?)
Systems like IBM Congos BI or Oracle OBIEE can be configured to include contextual information with each generated query, so you can quickly identify what user and what report spawned the query.
If we could flag individual client machines as needing to have SQL queries identified explicitly, then that also would probably solve this use case, and might even be a better solution.
I do realize that philosophically the current way this functions is ideal from a historical wait analysis perspective for most systems, but the cases where this is required tend to be ones that are very large and have a heavy impact on the databases systems in question. In the case of add-hoc reporting systems they tend to touch a lot of different databases, usually not in a positive manner from the perspective of the DBA. This type of a modification would allow accommodation for both use cases.
Thanks - great products - keep up the good work!
