Since we don't allow our DBA's to do analysis and tuning in our production we would like to be able to run QWT against the production catalog copy that we have in test. The workaround we have is not really comparable but we have a routine that can do a pre-bind with explain yes to a fake collection in production but it only works for static SQL and we are getting more and more dynamic SQL. The benefit would be that our DBA's would be able to use QWT with current production statistics even when they are not allowed to use the tool against the production systems.
Why is it useful?
|Who would benefit from this IDEA?||The benefit would be that our DBA's can use QWT in our test environment with production statistics for both static and dynamic SQL.|
How should it work?
We would like an option to change the schema for the catalog tables that QWT uses and point it to a catalog copy.
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions