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)?
© ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center