Access the answers to your technology questions today.
Subscribe Now
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
Subscribe Now
30-day free trial. Register in 60 seconds.
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Join the Community
by: MRomaniPosted on 2009-11-02 at 08:38:00ID: 25720896
My suggestion is to use Linq. Basically, create a database context, hit the databse and collect data that you need and store it in an object (can be done using Linq), maybe something like a list and then once you have your objects, you can search through them without slowing down your whole system due to repeated hits to your db, instead you'll be hitting your objects more, which is much faster.
So basically i'm suggesting to store the data in objects using Linq instead of creating temp tables to do work on, and then which might get deleted soon after anyways....this is the same, except it'll run faster and in my opinion is easier...
Hope i understood your question right, and hope this helps.