Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
CURSORs are neither good nor bad - they are just a tool.
The performance of the cursor is largely dependent on how many times it is executed (look at the referred post) and/or how large the resulting "found set" that will be returned. The query within the cursor is where performance may be improved or degraded.
Sometimes, the best solution is using a cursor - other times not even using SQL is a better solution (again, see the referred post).
Joined: 26 May 2005 Posts: 178 Location: Copenhagen, Denmark
Use EXPLAIN and figure out the performance of each query. Are the queries going for Index scan or Tablespace scan. Obviously 200 records cannot make much difference even if it goes to tablespace scan.
Get in touch with DBA to find the optimisation path. Are the indexes being used effectively..? Check the conditions in the WHERE predicate of all the queries. If applicable change some BIND parameters.