Thank you all folks who attended my Dublin presentations at OUG Ireland! It’s great fun to be back to the island again, and I enjoyed talking very much.

Thursday March 23rd 2017:

“42 (alternative?) Facts for Oracle Clusterware, ASM and RAC”.
Download pdf here.

Friday March 24th 2017:

“No Magic, no Jungle, no Swamp: The Oracle Alert Log”
Download pdf here.

Thanks everyone who attended the talks, you are a great crowd!
– Martin

Auf den Frankfurter IT Tagen 2016 liefen zwei Vorträge von Performing Databases aus dem Themenkreis Oracle, für die wir hier die Präsentationen kostenlos zum Download zur Verfügung stellen.

Vielen Dank an die zahlreichen Zuhörer und die tollen Gespräche im Anschluss!

“The Bad One Into Your Crop – SQL Tuning Analysis for DBAs (Die Schlechten ins Kröpfchen – SQL Analyse für DBAs)” (Slides)

“42 Fakten zu Oracle RAC, Grid Infrastructure und ASM” (Slides)

Thanks everyone who attended my Oracle Technology session “The Bad Ones Into Your Crop – SQL Tuning Analysis for DBAs” at DOAG Konferenz 2016 #DOAG2016. (German: “Die Schlechten ins Kröpfchen – SQL Analyse für DBAs”) – Martin Klier

Slides: The Bad One Into Your Crop – SQL Tuning Analysis for DBAs

Download Whitepaper (German)

Picking out, validating and improving slow or resource-eating SQL statements is part of any responsible DBA’s work who takes his/her job serious. Identification alone can be tough, but it will be even harder to improve something you have no chance to understand the purpose of. This way, you will never be in the position to improve elapsed time by factors of 1 million or 100.000 – that’s a privilege of the designers and coders. But there is a generic way for us database whisperers to approach bad-behaving SQL, and improve it by factor 2, 5 or 10. Sometimes this is all we will get, so let me show you how: We are avoiding expensive tools, voodoo features, concatenated heuristics and one-engine-fixes-the-other. An unspectacular, real-world, common-sense approach, reaching the goals with grassroots technology.

Objective 1: Understand the basic components of parsing SQL in Oracle Databases
Objective 2: Pick the culprit, understand its execution plan
Objective 3: Weed them out, avoid collateral damage.