SqlServer ASP.NET Session Replication

Curiously, have people set up 2-way transactional replication in the tables that ASP.NET uses for the saved state of the SqlServer session (ASPStateTempSessions and ASPStateTempApplications) and the tables used for membership, role and personalization? How did it happen? Were there any mistakes?

+3
source share
2 answers

For membership, you are probably well versed in replication, although a cluster may be better for scale. For the state, I would be more likely to use a cluster.

I would say that the exception is when you have a geographically separated set of servers, but websites are rarely found, with the exception of some of the largest, geographically separated.

Have I ever done replication in state or membership tables? no.

+1
source

It’s clear that you can do this, you just need to edit one of the stored procedures in which there is a small error in which you would encounter an error

The column name or number of values ​​specified does not match the definition table.

to avoid this only change TempGetAppID stored procedure

from this

INSERT [YOURDBNAME].dbo.ASPStateTempApplications
            VALUES
            (@appId, @appName)

TO

INSERT [YOURDBNAME].dbo.ASPStateTempApplications
            (AppId,AppName)
            VALUES
            (@appId, @appName)
+2
source

Source: https://habr.com/ru/post/1706969/


All Articles