CommandBehavior.SingleRow

  • Thread starter Thread starter Justin
  • Start date Start date
J

Justin

As far as performance is concerned, is it more efficient to set
SqlCommand.ExecuteReader(CommandBehavior.SingleRow) when you are only
dealing with single row?

Thanks
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

OleDbCommand returns same reader with different parameters 1
Using a DataTable instead of a DataReader 7
DataReader .HasRows but returns 'Invalid attempt to read when no data is present' error 3
Can't get Access Query to Work 2
Do I need to Close DataReader in USING? 2
IDataReader.Read() (wrong number of rows) 2
How to get the output parameter from Store Procedure ? 1
Call SqlCommand.ExecuteReader inside another SqlCommand.ExecuteRea 9

Back
Top