How to tame runaway SQL statements after a database, application or hardware upgrade?


DBA & Infrasturcture

Date and time






After upgrading databases, applications, HW or even after installing patch-sets it often happens that some SQL statements go wild, meaning they start performing significantly different compared to their behavior before the change. If performance is better then no one will complain, but if it is worse then you might have a problem.What options exist to confine the execution of such statements? How this can be done in DB Standard Edition environments?You will also find out how such SQL statements can be located.

Lecture details

Type: Lecture
Level of difficulty: Detailed
Experience Level: Experienced
Desirable listeners function: DBA
Group of activity: DBA & Infrasturcture

About speaker