SQL Database Mirroring and the Session State Database

[Calculated]

We have a number of databases mirrored including the ASPState session
database used by the websites. However the connection string to the
ASPState database does not allow you to include the 'Failover Partner =
ServerB' parameter, and it does require you to have the 'Data Source =
ServerA' parameter. (Where ServerA = Principal, ServerB = Secondary.)
Normal databases that allow you to have 'Failover Partner' parameter
work great.

How is possible to ensure that the ASPState database fails over or is
available if Server A goes down to ensure the continous operation of
the web application? The problem being that the Session connection
string has the server specified when the other db's have switched to
server B.

It is preferred but not essential that sessions remain intact - surely
there must be a workaround for this?

(Apologies for cross-post but I think this issue may have a .NET
resolution as much as SQL Server...)

TIA,
S.

[Don]

Hi There,

Did you get your problem solved? I got same issue here, we have couple of
web application on .net 1.1, recently we migrated to sql 2005 db with
mirroring on couple of dbs, however, connectionstring does not like "Failover
Partner"

Thanks
Don

"Calculated" wrote:

We have a number of databases mirrored including the ASPState session
database used by the websites. However the connection string to the
ASPState database does not allow you to include the 'Failover Partner =
ServerB' parameter, and it does require you to have the 'Data Source =
ServerA' parameter. (Where ServerA = Principal, ServerB = Secondary.)
Normal databases that allow you to have 'Failover Partner' parameter
work great.

How is possible to ensure that the ASPState database fails over or is
available if Server A goes down to ensure the continous operation of
the web application? The problem being that the Session connection
string has the server specified when the other db's have switched to
server B.

It is preferred but not essential that sessions remain intact - surely
there must be a workaround for this?

(Apologies for cross-post but I think this issue may have a .NET
resolution as much as SQL Server...)

TIA,
S.