How to tame runaway SQL statements after a database, application or hardware upgrade?
Track
DBA & Infrasturktura
Datum i vrijeme
-
Dvorana
-
Trajanje
45'
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.
Detalji o predavanju
O predavaču
Boris Oblak, autor
Boris Oblak, the head of research at Abakus plus, is in charge of the IT research department since 1992. He graduated in 1987 from Faculty of Mechanical Engineering at University of Maribor. He started working with Oracle database at version 5. He and his colleague were successful in porting Oracle database 7.1.5 to linux in 1996. At the time Oracle had not yet supported the operating system. With version 8 linux became an officially supported platform for the Oracle database. Since then Oracle uses linux as their primary development platform and focused their efforts into administration and optimization of their database. Boris is also a co-author of the Flight Information System application that is used at the „Jože Pučnik Airport“, which is the biggest airport in Slovenia. He is the main author of the Arbiter, which is an application for audit trail management. In the year 2004 he became Oracle Certified Professional DBA.