Results 1 to 5 of 5

Thread: Speed Difference Data Reader vs DataSet

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Sep 2002
    Posts
    90

    Speed Difference Data Reader vs DataSet

    Can anyone tell me if there is a real big speed difference between quering into a datareader as compared to a dataset.
    This could be a query ranging from pulling 1 record to 3000+ records.

  2. #2
    yay gay PT Exorcist's Avatar
    Join Date
    Apr 2002
    Location
    . . . my reason of shame
    Posts
    2,729
    If speed is really an issue then use DataReader whatever the number of rows you'll retrieve..

    If you want to change something etc maybe a dataset will be the best, it all depends in what you want
    \m/\m/

  3. #3
    Registered User Nucleus's Avatar
    Join Date
    Apr 2001
    Location
    So that's what you are up to ;)
    Posts
    2,530
    why don't you test it out yourself :shrug:

  4. #4
    Frenzied Member DevGrp's Avatar
    Join Date
    Nov 2001
    Location
    Charlotte, NC
    Posts
    1,256
    DataReader is always faster. The key is understanding the differences. That will make your choice a little bit easier. The DataSet is an in memory representation of the DB. So if you are gonna be doing and updates, deletes or adding new rows, I would suggest using a DataSet.

    DataReader is good for just getting the data to present to the user, since its using a forward only cursor.

  5. #5
    Fanatic Member VBCrazyCoder's Avatar
    Join Date
    Apr 2003
    Posts
    681
    When I tested this, the dataset used more memory and was slower than the datareader (which we all know) but the difference got narrow as we started pulling more data.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width