Moving Session Sate from InProc to SQLServer

Glayaar — Mon, 12 Jul 2010 03:08:05 GMT

Based on my discussion with the developer, he suggest that under such scenario, using large data, it will be better in using file state server instead of session for data storage as explained in this blog post.

You could also read more detail about fileserver storage in the WebGrid documentation on the article "DataCacheStorage Property"

The issue you encounter is probably caused because of the SQL row size limitation. Without a simple sample or more detail description for your scenario, we will not be able to replicate the issue in our environment.

Moving Session Sate from InProc to SQLServer

sfrench@sierradata.com — Fri, 09 Jul 2010 16:31:41 GMT

Hello,

We are in the early stages of development on moving our application's Session State from InProc to SQLServer. Up until now we've worked through serialization issues and other simple errors related to the change. Just recently we loaded a very large dataset into a WebGrid and ran into the error attached. After some testing we've found it's possible to get this 'Out Of Memory' error quite consistently when loading large numbers of rows into a WebGrid (version 7), especially when the machine is running low on RAM. We never received an error before moving to SQLServer session state mode but the performance of the grid in relation to combo boxes often suggested our session state was being recycled when too much information was loaded into the grid.

Can you offer any advice or direction on implementing this functionality without causing errors? In a perfect world we would not have grids that load so many rows in but in actual practice it often occurs. I would attach a sample project but for the SQLServer Session State mode to work you need to directly reference a SQL server and I don't know your internal setup.

Thanks in advance for any feedback,
Scott French
Sierra Data Systems

Intersoft Community - WebGrid Enterprise - Moving Session Sate from InProc to SQLServer

Moving Session Sate from InProc to SQLServer

Moving Session Sate from InProc to SQLServer