HI Stuart,
It doesn’t have anything but a minor effect on tempdb. I’m not sure why you’re imagining it will grow unchecked. They normally just create the asp.net session state tables with a database. It works fine and allows for high availability options. Alternately, there are memory-based services that you can install on a server that then provides session state storage for other servers. That can be faster for small server farms but doesn’t offer the HA options as easily. The only real issue I’ve seen with the asp.net session state database is when it grows to large numbers of sessions, some of the sprocs aren’t very well written and need to be modified. For example, they have a sproc that cleans up expired sessions. That’ll work fine until there are a large number to clean up at once. When that happens, they clearly hadn’t thought much about blocking. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: <http://www.sqldownunder.com/> www.sqldownunder.com From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Stuart Kinnear Sent: Thursday, 1 May 2014 4:32 PM To: ozDotNet Subject: SQL server session state I am considering using SQL server to maintain session state, to improve session lifetime in events such as IIS reboot. I was wondering if there are any downfalls in doing this. What I am bothered about is that over months of use the tempDB could grow unchecked. Is this something I need to worry about, are there real benefits ? -- ----------------------------------------------------------------------------- Stuart Kinnear Mobile: 040 704 5686. Office: 03 9589 6502 SK Pro-Active! Pty Ltd acn. 81 072 778 262 PO Box 6082 Cromer, Vic 3193. Australia Business software developers. SQL Server, Visual Basic, C# , Asp.Net, Microsoft Office. -----------------------------------------------------------------------------
