My scenario is that I have two webservers/database servers that I'm trying
to make redundant in terms of filesystems, web services, and database
services:
+ filesystems are replicated using server 2003 R2
+ web services are made redundant using NLB
+ databases are mirrored via SQL Server 2005 database mirroring.
I have ASP.NET and ASP applications that consult the database. These
applications are being mirrored by virtue of the fact that the filesystems
between the two servers are being mirrored. What I need to figure out is the
cleanest way to set up things so that my apps will initially try to
reference database server "A" for its data needs, and if that doesn't work,
to attempt to contact database server "B". Remember that the databases will
be exactly mirrored on both boxes, so no aspect of the DB schema should
change.
Is this capability built into any aspect of ASP.NET's data provider model?
For any fellow Classic ASP dinosaurs (freshly paid from MSFT's "Office has
evolved..have you" campaign :), can someone suggest a clean workaround in
classic ASP?
Thanks,
Ken Fine
University of Washington