Is datareader quicker than dataset when populating a datatable?

by

The DataAdapter uses a DataReader under the hood so your experience would likely be the same.

The benefit of the DataAdapter is you cut out a lot of code that would need maintenance.

This debate is a bit of a religious issue so definitely look around and decide what works best for your situation:

More Related Contents:

  1. .NET DataTable skips rows on Load(DataReader)
  2. Which method performs better: .Any() vs .Count() > 0?
  3. HashSet vs. List performance
  4. Why are multi-dimensional arrays in .NET slower than normal arrays?
  5. Performance of Arrays vs. Lists
  6. Is it better to call ToList() or ToArray() in LINQ queries?
  7. What’s so wrong about using GC.Collect()?
  8. Why is LINQ JOIN so much faster than linking with WHERE?
  9. String.Join vs. StringBuilder: which is faster?
  10. How to measure code performance in .NET?
  11. HashSet versus Dictionary w.r.t searching time to find if an item exists
  12. Why seal a class?
  13. .NET LINQ query syntax vs method chain
  14. How to convert json into datatable?
  15. Why is the first WCF client call slow?
  16. Do sealed classes really offer performance Benefits?
  17. Anatomy of a “Memory Leak”
  18. Can you get a Func (or similar) from a MethodInfo object?
  19. Entity Framework is Too Slow. What are my options? [closed]
  20. Horrible redraw performance of the DataGridView on one of my two screens
  21. System.IO.FileSystemWatcher to monitor a network-server folder – Performance considerations
  22. Optimum file buffer read size?
  23. How do I improve ASP.NET MVC application performance?
  24. Which is faster: clear collection or instantiate new
  25. Does .NET assembly size affect performance?
  26. IIS: web applications warmup
  27. Fastest way to convert datatable to generic list
  28. Entity Framework Find vs. Where
  29. Performance: XDocument versus XmlDocument
  30. WPF slow to start on x64 in .NET Framework 4.0

Leave a Comment