5 responses

  1. chet
    August 13, 2010

    I think I found DBMS_PROFILER just a couple of years ago. Pretty freaking awesome I must say.

    The reason no one knows about it is because most of us don’t care about it…or we’re just too far removed from the actual implementation to care. OK, it was last year I found it.

    I was debugging a 2500 line procedure where the BEGIN was on line 2000. I had to prove that this was thing was slow and also show the multiple, unnecessary, paths it took. It was quite fun to have that kind of evidence.

    I still don’t have a completely cogent thought, so I’ll just stop now before rambling too much.

  2. JeffS
    JeffS
    August 13, 2010

    Good point Chet. That’s more of my issue, the lack of ‘caring’

    Just code it, run it, forget about it…until something doesn’t do what it’s suppose to!

  3. Gary
    August 14, 2010

    I think the problem was that to use the profiler, you needed a couple of scripts run by the DBA. That made it hard for developers to try it to see whether it was useful, and without trying it, it was hard to justify to a DBA why the scripts should be run.

    • JeffS
      JeffS
      August 14, 2010

      you’re right on that Gary! That’s why I propose all Dev databases have this setup automatically. It’d be like giving a developer the the rights to create their PL/SQL but not run it.

Leave a Reply

 

 

 

Back to top
mobile desktop