Caching of records in asp.net or sql

Question

0.00/5 (No votes)

See more:

, +

Hello everyone,

I need some kind of caching mechanism in sql or in asp.net for storing data (records) retrieved from sql stored procedure..

Actual scenario :

I have one stored procedure in sql which fetches 7 tables and gives the result , the result obtained is too huge i.e. around 5000 records..

Now i display that records in asp.net gridview control which takes too long time to bind that record and display it on screen

Now when i insert some record suppose say 10 records, it will again execute that storedprocedure and fetch 5010 records and then will get bind to the gridview control

Please suggest something by which i could reduce this execution time which occurs in fetching record and displaying record in front end....

I need some way that i could store 5000 records and when 10 records are inserted , it fetches only 10 records and these 10 records are appended to those 5000 records...

Please suggest...

Regards,
Krunal Panchal

Posted 5-Sep-12 2:42am

krunal25

Updated 5-Sep-12 2:44am

v2

Add a Solution

Comments

Ankur^\m/ 23-Nov-12 2:07am

You call 5000 huge?! ;)

Paging is the way to go, as Dylan suggested! Also since you are making edits and if that is frequent, Caching isn't appropriate.

3 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)

Dylan Morley · Answer 1 · 2012-09-05T02:54:00

What you really want to do is implement a decent paging solution. This will solve both your problems, you won't have slow binding times and you won't use lots of server memory by caching larges amounts of data.

Humans can't handle 5000 records at once, it's too much information. Opinions vary, but for grid data I think 25-50 rows per page is about right - for what the eye can read and comprehend. So, if you're only displaying this amount of records at any one time, you only need to fetch that amount from your database. As you click 'next page', your grid can make an ajax request and fetch the next set of data to display.

Here's a GridView example using Update Panels http://www.c-sharpcorner.com/uploadfile/prathore/gridview-paging-and-sorting-using-ajax/[^], but I strongly suggest you spend a bit of time searching - that's quite a basic example.

Using this technique, we have grids that happily display thousands of records.

Christian Amado · Answer 2 · 2012-09-05T02:51:00

Solution 1

You will love this feature: SqlCacheDependency.
http://msdn.microsoft.com/en-us/library/9dz445ks.aspx[^]

Using SqlDependency for data change events[^]

Hope it helps

Posted 5-Sep-12 2:51am

Christian Amado

Shriantlandge · Answer 3 · 2012-09-05T04:02:00

Solution 3

You can use SQL paginiation techniq.
PLease check below URL :

http://shrikantlandge.blogspot.com/2009/05/pagination-with-mssql-server-2005.html[^]

Posted 5-Sep-12 4:02am

Shriantlandge