Thanks, Travis.
Before I try a db trace, I have another question related. I also ran the mxdPerfStat tool with the same map document and that gave me the time spent in 3 different phases- Geographic, Graphics, and Cursor phase. I understand that Cursor phase is the elapsed time of executing spatial query using iFeatureCursor to fetch data from DBMS, but I am sure if this Cursor phase includes some processing time from a local client too not only from DBMS. I can also see the Refresh Time in an xml result is the sum of Geography + Graphic phase excluding the Cursor phase then does this mean that it is independant from Geography Phase time?
Can you give me more details on how to distinguish the Cursor Phase from Geography Phase?
My understanding is that the Geography phase is the rendering time for fetched data, and the Cursor phase is not included in the Refresh time because it is not associated with Active View's refresh...But even though it is not part of refresh time, client processing is still associated with this Cursor time so I can't eliminate the client as suspect. Is this right?
Thanks for your help.