Re: OleDbCommand.ExecuteReader Performance
From: Sahil Malik (contactmethrumyblog_at_nospam.com)
Date: 01/20/05
- Next message: Sahil Malik: "Re: Relations in a three-thier app."
- Previous message: Sahil Malik: "Re: why dataset in ado.net is disconnected"
- In reply to: Elad: "OleDbCommand.ExecuteReader Performance"
- Next in thread: Elad: "Re: OleDbCommand.ExecuteReader Performance"
- Reply: Elad: "Re: OleDbCommand.ExecuteReader Performance"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 Jan 2005 07:17:26 -0500
Okay --- even in a web based environment, your server is what holds the
OleDbCommand instance, which is not communicating over HTTP to the
underlying database. So it's only as bad as the connection between your web
server and your oledb database is.
To get chunks of data instead - you can use DataTable/Dataset.
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"Elad" <Elad@discussions.microsoft.com> wrote in message
news:84ECAA3A-27E3-4788-8C1E-E172D7C8A821@microsoft.com...
> Hi,
> I have a question regarding OleDbCommand.ExecuteReader.
>
> From what I understand, ExecuteReader fetches rows on demand, on a row by
> row basis.
>
> What are the implications of using this method when your database is
> accessed over the web? Won't it be terrible slow? The reason I ask this
> is
> because it seems that each time I call OleDbDataReader.Read(), an HTTP
> request is sent to the server and one row of data is returned.
>
> Is there a better way of receiving user-defined chunks of data from
> databases? I would rather not use OleDbDataAdapter as it is too slow.
>
> Thanks.
- Next message: Sahil Malik: "Re: Relations in a three-thier app."
- Previous message: Sahil Malik: "Re: why dataset in ado.net is disconnected"
- In reply to: Elad: "OleDbCommand.ExecuteReader Performance"
- Next in thread: Elad: "Re: OleDbCommand.ExecuteReader Performance"
- Reply: Elad: "Re: OleDbCommand.ExecuteReader Performance"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
