Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Ravikumarc
Yak Posting Veteran
51 Posts |
 Posted - 2010-03-23 : 17:46:42
|
| Dear All,Can you please let me know how to create ASPstate database,Is there any script to create ASPstate DB.Thanks & RegardsRavi |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-03-23 : 20:35:50
|
| if yours is a high volume transactional system, i would strongly discourage you from maintaining http sessions in sql server |
 |
|
|
Ravikumarc
Yak Posting Veteran
51 Posts |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-03-25 : 16:29:42
|
| "if yours is a high volume transactional system, i would strongly discourage you from maintaining http sessions in sql server"We do that - is it bad?Session Cookie on user's browser. Passed to (all) Sprocs as "Session ID parameter"Table of Session Data - SessionID(PK), AttributeCode(PK), ValueMind you, we don't use much from the Session Data table - a dozen values, or less, per session.We find this more efficient than using Session State in (Classic) ASP, plus we can maintain session for as long as we like (we use variable amounts of time depending on what the user was doing)Also useful for debugging - we can see all the session state data that a session used - up to when it is purged (after 7 days I think) |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-03-25 : 16:47:40
|
Really? You've found it more efficient? My only experience with it was not good...hammered the database server pretty good. Then again, everything I saw in that shop wasn't good lol  |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-03-25 : 17:24:50
|
"All" of our application is in the database.The ASP stuff just does template replace of {TAGS} with data from Rows/Columns in the resultsets (well, a bit more than that! but most of the logic is in SQL)SProcs get the various snippets of HTML that make up the pageSome of those HTML snippets are Templates that are merged with, yet more!, SQL ResultSets to make HTML snippets (Grids of data, for example)Some actions result in SAVE Sprocs being called, but most are READ Sprocs that get data relevant for the page, and its various "panes"All the Sprocs are happy for parameters to be provided with Session Data, but any such parameters that are NULL go get the data from Session Table - and then return it in Output parameters - so the next Sproc doesn't have to, also, look it up again.I have no idea if this is good, bad or indifferent - its just how we've always done it.Key for us is that we can fix / change a single Sproc and none of the rest of the APP has to change. So QA for deployment of a fix is modest (whereas if we had monolithic ASP application we would be needing to bring in all sorts of other changes within that "point release" and all the sides effects that go with it, and [I think] massive QA before release).In fact we very rarely write a line of ASP these days, just Sprocs  ... although, as the saying goes, "If your only tool is a hammer all your problems are nails"  |
|
|
|
|
|
|
|
|
Creation of Aspstate db