| Author: veeresh 03 Jan 2007 | Member Level: Diamond | Rating:  Points: 2 |
u can store dataset in session varible.if the dataset size is large,then application performance will decrese.
Use session state variables to store data that is specific to one session or user. The data is stored entirely on the server. Use it for bulky or sensitive data.
|
| Author: veeresh 03 Jan 2007 | Member Level: Diamond | Rating: Points: 2 |
There are several factors to consider when implementing session variables in your application. The first and most obvious factor is the amount of concurrent users in your application. This means an estimate of the maximum amount of users logged into your system at the same time during your peak hours. If this number is in the 100’s for your system chances are your scalability will be fine given a reasonable amount of server RAM.
If your application has thousands of concurrent users you have to be much more careful about not only the amount of session objects, but the storage capacity of those objects. Consider 10,000 concurrent users each with 10K of session data and suddenly your ASP.NET worker process is consuming hundreds of Megs of RAM. Your scalability curve should always be linear, whereby your system resource usage is directly proportional to your number of concurrent users. If you notice your server memory decreasing at a greater curve with the more users you add, it’s probably a good idea to step back and do a performance review.
Outside of the concurrent user factor there are some general do’s and don’ts with session objects. You should always consider the storage capacity of the objects you place into the session. For example, you should never take the results of a database query and store it in the session. Datasets, datatables, dataviews should all be considered off-limits when it comes to session storage.
The best types of objects to place into the session are simple basic pieces of information which help provide shortcuts and a more customized user interface. User name, location, even basic preferences are good candidates for session storage because they don’t consume much memory.
|
| Author: Vadivel Mohanakrishnan 03 Jan 2007 | Member Level: Diamond | Rating: Points: 2 |
1. Yes you can store Dataset within a Session object. But be careful and have an eye on performance of your system.
2. Size of session depends on Memory of the system. If you are storing the session values in Database then it depends on the hard disk space.
Best Regards
Vadivel
MVP SQL Server
http://vadivel.blogspot.com
|