Best approach to load data from DB in memory (if needed)

Question

0.00/5 (No votes)

See more:

I am planning for a project that deals with all kinds of tax for multiple companies and users. I'll be using C# (winforms), layered architecture (UI, DAL, BLL and WebService) and SQL Server.

Application will be used by multiple users, where a single user will deal with hundreds (maximum thousands) records at a time, which will have to be loaded, updated and set.

I want your help in deciding if I have to load my data into objects on program's start-up or something, or go with loading data on demand. I'm not sure how to decide this, and in case data should be pre-loaded which is the best approach to use since data will have to be saved back to DB.

I know I don't have any code to post here yet, forgive me but I'm still in the planning phase so I'm asking a theoretical question.

Posted 6-Jan-15 23:30pm

saleem_deek

Updated 7-Jan-15 0:18am

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kornfeld Eliyahu Peter · Answer 1 · 2015-01-07T00:00:00

You gave almost no information on how your application will be used - and that's the key for such a decision you ask for here...
In any case I would not advise to pre-load data. If you have huge data it will demand huge memory to contain it, and that should be a waste. If your data is small it will not be a performance issue to load them on demand only...
What you may consider is using SQL caching to improve performance, however in a simple CRUD application that move a few thousands of records maximum in one step you will need nothing, only well designed DAL...

CHill60 · Answer 2 · 2015-01-07T00:25:00

I agree with Kornfeld Eliyahu Peter - don't pre-load, load data as you need it.

I'd be a little concerned if a user was dealing with hundreds of records "at a time" in a tax system but I think that is just me misunderstanding your requirements. However it sounds like you will definitely need to consider transactional processing ... e.g. see this CP article SQL Server Transactions and Error Handling[^]

Best approach to load data from DB in memory (if needed)

2 solutions

Solution 1

Solution 3

Add your solution here

Preview 0