Performance tuning SQL queries in Oracle

Click here to see additional details, references etc.

―――――――――――X――――――――――

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiReddit! Float This Post!Stumble this Post!Google Bookmark this Post!Yahoo Bookmark this Post!Live Bookmark this Post!Share this post on Facebook

6 Responses to “ Performance tuning SQL queries in Oracle ”

  1. [...] the video tutorial here if you haven’t [...]

  2. Nice talk. DB Performance is still a bit of a mystery to me. I usually log the times that each query takes and if they are long, then I’ll point them to an expert like yourself. At least I will know who to ask for advice next time I write a horribly slow DB query :-) ))

    Heinz

  3. @Kabutz, yes please feel free. Rather than manually logging the times, it would be more convienient – and helpful for the ‘expert’ – to generate a database level trace. Here is how to do that:

    http://repettas.wordpress.com/2008/09/19/oracle-10046-trace-for-new-users/

  4. With P6Spy, you have a JDBC driver that logs the times automatically. The beauty is that it is database independent, so I can apply the same technique whether the customer is using Sybase, DB2, Oracle, MySQL, etc. Once we have discovered that the database is indeed a bottleneck, we would pass that information to someone like you who can then run a detailed trace. Thanks for the link for Oracle though :-)

  5. Hi Hardeep,

    I found your session quite informative, i want to learn how explain plan works and how can I understand explain plan and the terminology used in it, to tune my code. is this something you can help? any article ? book ? examples ?

Leave a Reply

You can use these XHTML tags: <a href="" title=""> <abbr title=""> <acronym title=""> <blockquote cite=""> <code> <em> <strong>

Subscribe without commenting