I've been tasked with investigating how to handle situations where our database server is inaccessible.
If our DB is missing, the entire site blows up because it can't initialize the session, even if the page the user is browsing to has content that doesn't depend on the session.
Ideally, I'd want the site to fall back to running "InProc" if the SQL server connection fails. Is there anything in the framework that would let me do this? Am I stuck creating some horrible mash-up of InProc and SQL in a custom session provider?
I'd be okay with just catching the error and continuing, but I can't figure out where to catch it. If I do Page_Error/App_Error, it's too late to just skip the session bits and deliver a partial page.