|
Home > Archive > IIS Index Server > May 2004 > ado.net and maximum rows
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
ado.net and maximum rows
|
|
|
| hi all,
it appears that ado.net doesn't support specifying maximum
rows, nor "top" is supported in sql select of index server
catalogs.
any workaround, other than breaking the datareader loop
after x iterations?
correct me if i'm wrong, but i assume by the time
i'm ready to loop-read the datareader, the damage is
done and the index server has already been subjected
to full stress. breaking out of the loop won't help
optimize anything, right?
i'm pretty sure that this is true for dataset retrieval.
thanks,
rh
| |
| David Lee 2004-05-18, 8:36 pm |
| Unfortunately, the only workaround is to use tlbimp and generate a COM
wrapper for ixsso.
Command properties aren't supported in ado.net (though I don't understand
why).
"rh" <rhashemian@hotmail.com> wrote in message
news:56c3b705.0405181015.7912ef34@posting.google.com...
> hi all,
> it appears that ado.net doesn't support specifying maximum
> rows, nor "top" is supported in sql select of index server
> catalogs.
> any workaround, other than breaking the datareader loop
> after x iterations?
> correct me if i'm wrong, but i assume by the time
> i'm ready to loop-read the datareader, the damage is
> done and the index server has already been subjected
> to full stress. breaking out of the loop won't help
> optimize anything, right?
> i'm pretty sure that this is true for dataset retrieval.
>
> thanks,
> rh
|
|
|
|
|