>> Hi,
>>
>> |
>> |I don't understand what you are asking for "actual PLANs for each case?"
>> |
>>
>> Each statement has an execution PLAN that tells what "path" the engine takes to get the desired records.
>>
>> If you can narrow WHAT is the 'problematic' statements your app is running and then execute them using some client like ISQL or FLAME ROBIN, you'll get to know the execution plan and statistics from the engine.
>>
>> That information may help finding what's going wrong.
>>
>> As an alternative, and very easy way to find your what's wrong, is enabling fb AUDIT (or start a trace session) -- since you're rinning fb 2.5 -- and run your application. Than Fb you show you whats going on!
>>
>>
>> =)
>>
>> Regards,
>> Anderson
>>
>
> Again, thanks for your quick response.
> Can you give me some guidance on how to enable FB AUDIT?

Read my article here:
http://www.ibphoenix.com/resources/documents/general/doc_3

Then either use the command-line utility fbtracemgr and/or our FB
TraceManager product: http://www.upscene.com/go/?go=fbtm


--
With regards,

Thomas Steinmaurer
Upscene Productions
http://www.upscene.com
http://blog.upscene.com/thomas/

Download LogManager Series, FB TraceManager today!
Continuous Database Monitoring Solutions supporting
Firebird, InterBase, Advantage Database, MS SQL Server
and NexusDB!