Up to now both Birmingham and Ukoug conference were very satisfactory, I enjoyed the first three days very much. After a 30-45 minutes random walk we found at the end of the New Street the St Martin’s Church, a beautiful scene since it is Christmas time, and two books stores near the Church which I will be mining tonight after Ukoug ends. Also as they told me, “Once pubed, never stopped”, this is a reality in fact, and can easily ruin the conference :)
DB Time Performance method by Graham Wood
Programming real applications with Application Express by Andrew Woodward
Every Performance Problem Is One Of Two Things by James Morle
And here comes my second great presentation at Ukoug, John was prepared well and he was excellent during the presentation. Debugging APEX Applications by John Scott
Modelling on the cheap by Andrew Clarke
Real World Database Recovery – An Experience by James Hetherington
Understanding and Interpreting Deadlocks: What to do with an ORA-00060 by Mark Bobak
PL/SQL Tracking and Tracing Instrumentation for Developers by Tim Scott
Extending Security with Oracle Database Vault by Joel Goodman
Swingbench, When you need a load by Dominic Giles After this presentation since I am a PL/SQL dinasour :) I thought this can be done easily within Oracle, why not an open source project based on DBMS_SCHEDULER and APEX technology for inputs of load and reports. Hüsnü has already a loading Oracle series, and maybe there is already some.
After surviving 10 sessions on my third day today it will be a child play I guess :) But because of the long way waiting back to home I plan to post the last day’s notes on this Sunday.
Extract(Read) > Transform(Test&Apply) > Load(Learn) Blog 
I saw Johns presentation at OOW, he did really well and it was very interesting! I like his style of showing things.
BTW, instead of “if v(‘DEBUG’) = ‘YES’ then” you can also use the global variable “if apex_application.g_debug then” which is a little bit nicer because there is not so much hard coding. Anyway, the IF can be skipped if the apex_application.debug procedure is used for logging, because it will automatically do the IF inside the procedure.
Have fun in UK
Patrick
Thanks for the very kind feedback, it was a *HUGE* hall and it was really difficult to see the audience to see whether people where yawning or looking with interest!
Patrick,
You must have been jetlagged at OOW as I covered g_debug there and mentioned about the hard-coding too ;)
John.
For many practical purposes it may be good to use a PL/SQL based loading toolkit. But notice that when you measure with a tool within the environment itself you also measure the latencies, waits, execution time due to PL/SQL or DBMS_SCHEDULER functionality. So measuring with a tool out of the test environment will be a better approach as SW does.
John, I remember that you said that during your presentation. You had 100% of my attention! :-)
I just wanted to point it out again. Because Tonguç nodes also contain the “hard-coded” version, but which in my personal opinion isn’t the best version and shortest version to use.
Patrick