Optimization profile

Description: This request is to provide an optimization profile that may be applied at the DB layer, i.e., meaning no application code would need to be modified to use the profile, and the profile is configurable to where no instance recycle (start/stop) or DB activation (deactivate/activate) is needed.

When the optimization profile is in effect, the DB would match SQL submitted to the profile and use the guidelines provided in the profile.

Why it’s not feasible to use the connect procedure to set the optimization profile:

Using the connection procedure would require every connection to have the extra overhead of checking if the optimization profile is applicable, when only a subset of queries need to use the optimization profile. Our environment is also sensitive to changes in runtime since there are thousands of connections and millions of queries run in short time frames.

Imbedding the “set optimization profile” in the code is not reasonable, since there are many application teams across the organization that would need to be changed and its unlikely this would actually happen.

Currently when the statistics aren't aligned w/the data due to data inserts/loads/other reasons it can cause poor performance.

We have had poor access plan cause system issues where the application is virtually unusable..

This suggestion is to allow an alternative method to address statistics and optimization profile so its easier to address access plan issues.