DataReader vs. DataTable

Posted on 2011-02-10
Last Modified: 2012-05-11

I have the following code listed below and would like to know which method would be better to use, either a DataTable or DataReader. The content that this code retrieves will hardly change but it's data is tied to other data for reasons that I cannot make it static within the site.

This code below is called in 20 different pages. The same code in each 20 pages called each time a user visits each of those 20 pages.


    protected void Page_Load(object sender, EventArgs e)

    protected void Retrieve_NavLinks()
        using (SqlConnection conn = new SqlConnection(ConfigurationManager.ConnectionStrings["Test"].ConnectionString))
            SqlCommand cmdRetrieveNavLinks = new SqlCommand();
            cmdRetrieveNavLinks.CommandText = "PicksPhoto_RetrieveNavLinks";
            cmdRetrieveNavLinks.CommandType = CommandType.StoredProcedure;
            cmdRetrieveNavLinks.Connection = conn;


            SqlDataReader rdr = cmdRetrieveNavLinks.ExecuteReader();

            rpRetrieveNavLinks.DataSource = rdr;


ALTER PROCEDURE [dbo].[PicksPhoto_RetrieveNavLinks]


SELECT navm.mnav_id, navm.onav_id, navm.mnav_linkname, navm.mnav_url
FROM [App_NavMain] AS navm
INNER JOIN [App_NavOrder] navo
ON navm.onav_id = navo.onav_id
WHERE navm.mnav_id > 1
ORDER BY onav_id ASC

Question by:asp_net2
  • 2
  • 2
  • 2
  • +2
LVL 21

Expert Comment

by:Dale Burrell
ID: 34867281
A DataReader maintains a connection to the database for the entire time you are reading the data, and the data is delivered as you ask for it. A DataTable pulls all the data from the database into the DataTable construct and then lets you do all sorts of things to it.

Generally a DataTable will be slower and more memory intensive.

In your situation could you consider caching the data for a period of time to avoid having to pull it every page load?
LVL 29

Expert Comment

ID: 34867312
OK, I'm not quite sure about other complications for your app but I'd probably (especially for ASP) I'd choose Datareader.

The main and very important advantage - performance. I believe for on-line apps it's crucial.

It's easier to work with tables, definitely.

Probably, volue of data is important. If it's small - DataTable would be OK and fast enough.

Also. datareaders have other drawback. Please read the article:

Author Comment

ID: 34867533
Could you show me example how I would cache the code I have above? Is there anything I have to enable for caching?

I guess I'm a little confused, I was hoping of a solution that would somehow prevent 20 hits to my DB for the same data as in the code above.
LVL 21

Expert Comment

by:Dale Burrell
ID: 34867568
Well your question said "would be better to use, either a DataTable or DataReader" - which has been answered.

It sounds like you also want to know how to improve the performance of the site. Firstly it depends how often and under what circumstances the data changes. If having considered that you determine that you can afford to cache the data for a period then you need to consider it the data the same for all users in which case look at caching ( if it differs from user to user then consider using a session variable (

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline


Author Comment

ID: 34867601
The data will hardly ever change. All users need to see the same data. I plan on expecting thousands of hits per day.
LVL 29

Expert Comment

ID: 34867750
OK, this definitely needs caching to avoid DB traffic, I'd say. Not quite sure how this is done in ASP correctly - should be on Google.
LVL 14

Accepted Solution

systan earned 500 total points
ID: 34868566
if where you are comfortable to use your code?, then go for it.

Using dataReader is faster and a direct memory use.
Using dataTable can be filled if another data component to be called, like, dataRow, or dataAdapter.

As long as I remember when I benchmark these to component, it was a 2 seconds difference in a hundred thousand records.

DataReader vs. DataTable ?
Winner is DataReader

like I said "where you are comfortable to use your code?, then go for it."
it only matter a second or 2 or maybe 3 for a million records.
LVL 11

Expert Comment

ID: 34870546
LVL 14

Expert Comment

ID: 34871329
The best way to optimized your web performance is the way you handle your configurations,  and the code structures you wrote if is clean and simple.


Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

Just a quick little trick I learned recently.  Now that I'm using jQuery with abandon in my applications, I have grown tired of the following syntax:      (CODE) I suppose it just offends my sense of decency to put inline VBScript on a…
User art_snob ( encountered strange behavior of Android Web browser on his Mobile Web site. It took a while to find the true cause. It happens so, that the Android Web browser (at least up to OS ver. 2.…
It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now