| Subject | Re: [IBO] fastest IB_Cursor... how??? |
|---|---|
| Author | Helen Borrie |
| Post date | 2006-09-06T01:17:43Z |
At 10:17 AM 6/09/2006, you wrote:
IB_Cursor fetches each row one-by-one. If "performance" means speed,
you are measuring the time elapsed between when you call First and
when the first record appears.
Presumably, you are using IB_Cursor because you want to do some
non-visual processing on a set (since IB_Cursor does not store
records in a buffer). If what you are doing is slow and is not
touched by human hands, you should consider performing the operation
as a searched one, via a DML statement in an IB_DSQL, which would be
faster than anything you might achieve by pulling the set over to the client.
Helen
>What properties must i configure to get the fastest as posibleWhat do you mean by "better performance"? Is your routine slow?
>IB_Cursor??... the data are just readonly and all the records in the
>cursor are nedded..
>
>i just put "CheckRequired" to False cause is just for readonly
>purposes, and "ReadOnly" to True, but i want to know if there are any
>other porperty that i could set to gain better performance???
IB_Cursor fetches each row one-by-one. If "performance" means speed,
you are measuring the time elapsed between when you call First and
when the first record appears.
Presumably, you are using IB_Cursor because you want to do some
non-visual processing on a set (since IB_Cursor does not store
records in a buffer). If what you are doing is slow and is not
touched by human hands, you should consider performing the operation
as a searched one, via a DML statement in an IB_DSQL, which would be
faster than anything you might achieve by pulling the set over to the client.
Helen