>>Nadya,
>>
>>If it is for a report (i.e., read-only), you might try breaking it into pieces - for instance, first do one inner join, and then (with the result) the other inner join.
>>
>>I sometimes got drastic improvements with this technique.
>
>Good idea, I'll try. This cursor is used eventually to display data in a grid (for management statistics forms - e.g. I'm showing how many accounts each user has in his/her queue).
Mainly, what I meant with "R/O" is that you are not using the data in a view, which will send the data back to the underlying table. For a view, splitting the query into pieces may be unfeasible.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
