SqlCommand.ExecuteReader takes too much time

[Achim Domma]

Hi,

I have a table containing about 14,5 million records and I want to
iterate over the complete data. If I execute a "select * from
mytable", the call to ExecuteReader takes some hours to return. In T-
SQL I can open a cursor and start reading immediately. As far as I
understand, ExecuteReader/SqlDataReader should behave the same way -
but it seems like I'm wrong. Any hint?

regards,
Achim

 

[Mary Chipman [MSFT]]

What are you doing with 14 million rows? There are better ways to
export data from SQL Server. If you really want to use a reader, then
supply the nolock query hint to speed things up. See
http://blogs.msdn.com/sqlcat/archiv...s-might-be-missed-if-nolock-hint-is-used.aspx
for more information.

--Mary

 

[Cor Ligthert[MVP]]

Achim,

Are you starting your "T-SQL", whatever you mean with that as the
DataReader uses as well T-SQL, from the same machine as your DataReader?

Cor

 

[Cor Ligthert[MVP]]

I'm with Mary.

That Summit brings everybody together.



Cor

 

[Achim Domma]

That Summit brings everybody together.

Hi,

thanks to you all for your feedback. I'll think about redesigning my
process.

regards,
Achim