Last post Jul 06, 2017 07:00 AM by Cathy Zou
Jul 05, 2017 06:36 AM|alpeshataspnet|LINK
I am using SQL Server Session Mode in by WebForms application. Also, I am using ASP.NET Personalization and Profiles. While using these features of ASP.NET, we provide the SQL Connection String in config files.
Now, my question is that - Can we have "High Availability" feature for Session, Profile and Personalization databases of ASP.NET?. If the database goes down, then also the Session/Profile/Personalization features of application should not be affected. How can
I achieve that?
For, my appliation code, we have our custom code which handles the database calls while database failover occurs. But, we do not have control over database calls occurring for Session, Profile and Personalization. So, I am not sure, how I can do that.
Thanks and Regards,
Jul 05, 2017 07:12 AM|XIII|LINK
what could be used is the default in memory strategy (already faster than SQL Server) in combination with sticky sessions so that a call from a specific user always lands on the same server.
Other ways are fail over strategies of SQL Server. Likely best to be discussed with your DBA's and infrastructure architects.
Jul 06, 2017 07:00 AM|Cathy Zou|LINK
As far as I know, High availability is a system design approach and associated service implementation that ensures a prearranged level of operational performance will be met during a contractual measurement period.
And it could include multiple database and application server connected in a clustered environment with redundant hardware. One of the method to make ASP.NET application available even if one server goes down it so make your application connect to secondary
db server in the even of failure to connect to first server.
Following article introduces several SQL Server high-availability solutions that improve the availability of servers or databases.
A high-availability solution masks the effects of a hardware or software failure and maintains the availability of applications so that the perceived downtime for users is minimized.