Thanks vlad

but in a highly multithread environment, i m affraid that the time i get
the isc_info_read_idx_count and the time i execute my statement them lot
of other statement can be already done :(
so taking again just after the isc_info_read_idx_count can not be
accurate :(

On 12/1/2010 1:37 PM, hvlad wrote:
>
> > s their a way to retrieve the IDX_READS and the SEQ_READS of a
> statement or a transaction Without doint a select in the monitoring
>
> Look at isc_database_info call. You need isc_info_read_seq_count and
> isc_info_read_idx_count tags.
>
> Note, this stats is per-database, not per-statement. So you need to
> obtain stats before and after statement execution and compute a
> difference. This is exactly how isql (and other tools) works.
>
> Also note that for SS it will show you cumulative stats of all
> connections at given time slot. For CS\SC it is not a problem as it
> have this stats per attachment.
>
> Regards,
> Vlad
>
>


[Non-text portions of this message have been removed]