If SQL Optimizer is called from another Quest application, by default, the job is automatically sent to Batch Optimizer and it tries to start the job. In some cases this causes the system to hang or takes too long and is not what I wanted to use in the first place.
I would like the option to make settings and connection changes before running anything in the optimizer, or to choose what Optimizer feature I would like to use before anything is run.
How do you stop running the job automatically in batch optimizer and change what default window my SQL is sent to(like send to SQL Tuning instead)?
If SQL Optimizer is called from another Quest application, by default the SQL is sent to Batch Optimizer and the job is started automatically, using the connection which was active in the calling program.
In version 7.2 and older, there is no way of changing the default window of Batch Optimizer.
SQL Optimizer 7.2 and older - Stop running the job automatically so that changes can be made before running the job.
1. Launch Quest SQL Optimizer for Oracle as standalone.
2. From the top right of the main Optimizer window, click 'Options'
3. Select 'Batch Optimizer'
4. Uncheck 'Automatically start extracting SQL when job is added'
5. Close Optimizer
This will set the application to not start processing SQL automatically. The SQL will still be automatically sent to the batch optimizer and carry over the calling application's connection information, but it will now be possible to adjust setting before running any jobs in Optimizer.
SQL Optimizer 7.3 by default is now set to "Ask me every time" which prompts the users to select the module each time a test is sent to the SQL Optimizer from another application.
The option can be adjusted under Options | General | Options and allows a user to choose where to send SQL when received from other applications. Choose to send to "Batch Optimizer", "SQL Tuning", or "Ask me every time".
If SQL is set to open in "SQL Tuning", the job will not be automatically run.
If SQL is set to open in "Batch Optimizer", the option 'Automatically start extracting SQL when job is added' may still need to be adjusted to individual preference.