Since it's the logic within your stored procedures that is involved, you can use procedure profiling to narrow down the procedure, or statements within a particular procedure, to determine where your application is spending the greatest amount of elapsed time. Once you've narrowed it down to a statement or statements, then you can use SQL Anywhere's application profiling functionality in Sybase Central to log the statements (and their graphical plans) that were executed, and then use this information as the basis for your problem determination.
There are a large number of differences between Version 6 and Version 11. The server has a multitude of improvements in query optimization and execution, and will now cache the plans of SQL queries used within procedures. One thing you could do immediately is to re-test your application with plan caching disabled (set the option MAX_PLANS_CACHED to zero) to see if plan caching is having an adverse affect on your application's performance.
There are a large number of other performance indicators and counters that may be relevant to you for debugging this problem, but using procedure and application profiling first will likely help to narrow down where the issue occurs.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.