API Cursors

  • Hi Guru,

    My company, every thing we need is to buy from a vendor. However, we have PEOPLESOFT CRM app that has around 6000 tables and around 5000 views and none stored proc. We start seeing the slowness of the app. When I started running a trace to capture some data, and there is no useful info other than built-in API sp cursors in the following below:

    sp_cursoropen

    sp_cursorfetch

    sp_cursor

    sp_cursorclose

    What is the best way to capture SQL statements when I see very high READS? If I tell the peoplesoft prorammer guy to capture SQL statements from application, will he be able to do it?

    I just need the SQL statements to look at execution plan before I throw out some useful indexes.

    Please help!

    Thanks so much,

    Silaphet,

  • Doesn't the cursorOpen proc call give you the code for the select statement?  They are using server-side cursors - perhaps if they used client-side cursors things might perform a bit better (locks held for less time possibly).

  • SET RANT_MODE ON

    It's PeopleSoft (or as I used to call it PeopleS_it) .. I worked on a number of of their systems. You've got to use People  'this' and People 'that'. Every installation always ran poorly. The queries undoubtetly need fixing. They probably have a number of 'fixes' that you need to apply.

    SET RANT_MODE OFF

    You can use the Profiler to capture the SQL, but my guess is that its just the app code that needs tweaking. Also, once you get it working you'll have to run Profiler again because a number of tables are poorly indexed ... you won't find out until the tables grow big enough to catch your attention. Good Luck.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply