Hello Jason,

>>>>> Even with the settings above, I still have a large number (pretty much
>>>>> the number of Locate() calls) of
>>>>>
>>>>> SELECT * FROM IBLM$COLUMNLOGDEF
>>>>> WHERE IBLM$COLUMNLOGDEF.TABLE_NAME=? /* BIND_0 */
>>>>> AND IBLM$COLUMNLOGDEF.OPERATION=? /* BIND_1 */
>>>>> AND IBLM$COLUMNLOGDEF.COLUMN_NAME=? /* BIND_2 */
>>>>>
>>>>> calls. In the Firebird 2.5 Trace API output.
>>>>
>>>> I have a simple sample application with a smallish Firebird 2.5
>>>> database, which shows this problem. Care to have a look?
>>>
>>>
>>> Sure, I'd be glad to.
>>
>> Have you had time to give it a try?
>
> I have worked on this some and I am yet baffled about what is going on. I
> think there is an issue I should resolve in order to increase the
> efficiency.
>
> I'll be getting back into it again soon now that I am home from being out of
> town for over a week.

Has anything changed in that area in the newest 4.9.14 Build 5 release?

Thanks!


--
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!