I'm using SQLServer to store my ASP.NET session state. I also have several web servers which are connected via load balancer. Each server store it's session in the SQLSerer DB. The problem here is that the DB is a single point of failure.
My question is - how can I store my session across multiple SQLServer servers and be able to get the most updated data from each of them?
How well would the rest of your app perform if the database was down? This question is really about high availability of the database. You could add failover clustering to your SQL Server, which can get expensive. Or you can store your session in a distributed cache, such as memcached, redis or AppFabric.