How to store large DataSet at Client Side

Question

0.00/5 (No votes)

See more:

I have an application where i display the results in some of the thousands (25-40 thousands). On one page i display 125 records. here i need to store the dataset at client side so that on next pages he can see next records without any hit on DataBase.

I tried it with ViewSate,Cache and Session Object but none of these are successfull.

1. Viewstate is taking time due to more roundtrips, but its working well on Localhost.
2. Cache is not working. Search Results are conflicting with onw and another users.
2. Session is not working. Search Results are conflicting with onw and another users.

Posted 12-Jul-13 18:26pm

Ravi Kumar Shakya

Add a Solution

Comments

Mahesh Bailwal 13-Jul-13 1:24am

I believe you should cache this much amount of data in memory as it may have adverse impact on your performance and its not scalable. You should better go for retrieving Page data from SQL Server. Please check below links

http://www.codeproject.com/Articles/18148/SQL-Server-2005-Paging-Results
http://blog.sqlauthority.com/2013/04/14/sql-server-tricks-for-row-offset-and-paging-in-various-versions-of-sql-server/

1 solution

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)

Parwej Ahamad · Answer 1 · 2013-07-12T19:13:00

I think so any authenticated solution but I will have some idea which you follow:

1. Store all data into Browswer Cache and use any third party javascript api to access the data
3. Store all data in Cache and fetch data through Ajax call
4. Use Paging on Sql Server side and go with normal process