Re: How does sql ExecuteReader() work?

Incidentally, this is an ADO.NET question. Perhaps you might try that newsgroup...

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Avenger" <Avenger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4DBAFD35-17BA-4BC6-9DE7-AC3426FD9F9D@xxxxxxxxxxxxxxxx
Hello,
I'd like to get a good general idea of how ExecuteReader works, behind
the scene. Obivously it executes what ever sql statement you passed in your
SqlCommand. But once that's done, is all the information passed back to your
application right away, or is the information taken one record at a time from
the database using the Read() command.

Does the database create a "temp memory" location where it holds this
request, and passes row by row back to the application with each Read(), or
does it shoot back in one shot the whole request back to your application,
and your SqlDataReader holds all the information, and the Read() simply let's
you handle each row one by one and do what ever you need to do with it.

Thanks for any help with this inquiry.

.

Relevant Pages

  • Re: Using SQl to store aspx pages and memory problems
    ... I've seen classic ASP applications design this way that work ... database isn't some sort of magic pixie dust that solves all problems. ... > the memory increases - the slowness of the request could be dealt with by ... >> takes to get the page from SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Ado SQL Concept question.
    ... Once I get on a real database server (does MSDE ... Each user/session may request information about ... For SQL server a query will be best. ... Cursor type can be forward only if you only need readonly but that won't get you ...
    (borland.public.delphi.database.ado)
  • RE: connection to ado.net object
    ... The vb.net code will that submit the request for data to the hp> mainframe by using http and xml. ... This will somehow need to> include a connection object and statements oh how to connect to the SQL> server 2000 database. ... The user name and password are suppose to be passed to> the sql server as part of the connection string. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SQL Server 2000 and Latching problem
    ... Here is a brief definition of what latches are used for by Tom Davidson: ... > as the clients could talk to the database directly. ... > anything if the SQL server is dedicated or not. ... > than translate the original ISAM request. ...
    (microsoft.public.sqlserver.connect)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)