daveg92656
New member
- Joined
- Sep 27, 2006
- Messages
- 1
- Programming Experience
- 3-5
Howdy all,
For an asp website, is it better to carry application data around in SQL tables or in the Session or Application Object?
I’m integrating an online product configurator with a shopping cart application.
This is basically an aspx page which displays configuration details in a combo box fashion, allowing the user to choose which options they want.
There are 10 sql tables (in base product) which hold the configuration details.
So, I need to extract this data to display/populate on another page.
I’m wondering if I should use SQL tables to carry around the data or use the Session Object? If I use SQL tables, should I use Temp tables or the 'straight-up regular' tables?
How large can the session object get before performance issues come up?
Thanks for your help!!
Dave.
For an asp website, is it better to carry application data around in SQL tables or in the Session or Application Object?
I’m integrating an online product configurator with a shopping cart application.
This is basically an aspx page which displays configuration details in a combo box fashion, allowing the user to choose which options they want.
There are 10 sql tables (in base product) which hold the configuration details.
So, I need to extract this data to display/populate on another page.
I’m wondering if I should use SQL tables to carry around the data or use the Session Object? If I use SQL tables, should I use Temp tables or the 'straight-up regular' tables?
How large can the session object get before performance issues come up?
Thanks for your help!!
Dave.