sqldatareader compare to server side read only cursor in ado
From: z f (zigi_at_info-scope.co.il)
Date: 09/06/04
- Next message: William \(Bill\) Vaughn: "Re: sqldatareader compare to server side read only cursor in ado"
- Previous message: Kevin Yu [MSFT]: "RE: Error: Can't create child list"
- Next in thread: William \(Bill\) Vaughn: "Re: sqldatareader compare to server side read only cursor in ado"
- Reply: William \(Bill\) Vaughn: "Re: sqldatareader compare to server side read only cursor in ado"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 6 Sep 2004 06:58:04 +0200
Hi,
SqlDataReader must be connected to the database in order to bring data.
this is like server side cursor read only in ado.
the point is that in the SQL Profiler, when my code is running over the
records in ado recordset with server side cursor, i see SQL activity for
each move in the record.
in SqlDataReader i don't see the same activity in the profiler for each
record.
can someone explane why is the difference and is the DataReader really a
server side cursor?
TIA, z.
- Next message: William \(Bill\) Vaughn: "Re: sqldatareader compare to server side read only cursor in ado"
- Previous message: Kevin Yu [MSFT]: "RE: Error: Can't create child list"
- Next in thread: William \(Bill\) Vaughn: "Re: sqldatareader compare to server side read only cursor in ado"
- Reply: William \(Bill\) Vaughn: "Re: sqldatareader compare to server side read only cursor in ado"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|