User runs a job in the Batch Optimizer. The Batch Optimizer was not able to find a better alternative for the batch, but suggests optimizer can still run on each individual SQL. When the user tries to optimize the SQL statement, it processes the SQL for a while then they eventually get the error:
Failed to optimize.
Out of memory
Afterwards trying to delete the Job from the Batch Optimizer crashes SQL Optimizer.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center