Complex stored procedures that have multiple selects, updates and inserts produce an error. It might be impossible to split up each statement because each of them depends on the previous one.
If a user tries to to send to the SQL scanner against this stored procedure and tries to get a plan for a stored procedure, it gives the error "This type of SQL Statement is not supported."
Trying to get a plan or optimize a stored procedure, which is not a supported action.
STATUS:
Enhancement request ST41306 has been submitted to Development for consideration in a future release of SQL Optimizer for SQL Server.
The optimizer can only optimize one single SELECT/INSERT/UPDATE/DELETE statement at a time. The best way is to use the SQL Scanner to scan the SQL/SP first, identify them under different performance categories, and then send the individual SQL to optimize if they are problematic SQL.
