Post reply

ASP.Net Session State via SQL Server - tempdb

  • January 22, 2003 at 4:10 pm

    #447016

    Yes, whilst asp and aspx run within the same web, the session state provided by MS doesnt allow the two to mix in any way. You need to create your own custom solution to let the different universe's cross over in any meaningfull way.

    Here is a start for those considering :

    CREATE TABLE [dbo].[Session] (

    [sessionDateTime] [datetime] NULL ,

    [sessionId] [int] IDENTITY (1, 1) NOT NULL ,

    [sessionKey] uniqueidentifier ROWGUIDCOL NULL ,

    [sessionRefresh] [int] NULL ,

    [sessionCreateTime] [datetime] NULL ,

    [sessionArchive] [bit] NULL ,

    [sessionAccountId] [int] NULL

    ) ON [PRIMARY]

    GO

    CREATE TABLE [dbo].[sessionData] (

    [sessionDataId] [int] IDENTITY (1, 1) NOT NULL ,

    [sessionDataSessionId] [int] NOT NULL ,

    [sessionDataName] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,

    [sessionDataValue] [varchar] (250) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,

    [sessionDataCollection] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL

    ) ON [PRIMARY]

    GO

    you just need to create your own VB Script Class and VB.Net Class to access these structures ! The sessionID and sessionKey can be stored as cookies locally, like with the normal session object that isn't running in cookieless mode.

Viewing post 16 (of 15 total)

You must be logged in to reply to this topic. Login to reply