classic ASP: automatic failover to a secondary database

Report · May 16, 2006

SQL Server 2005 has a very nice feature called database mirroring that keeps
two databases on two boxes in sync. Seamless failover to the secondary
server is built into the .NET data provider:
http://msdn2.microsoft.com/en-us/library/5h52hef8.aspx

This is a neat trick. I need to be able to do something similar for my
Classic ASP applications.

The typical method for DB failover seems to be to store a connection string
in global.asa or somesuch and manually switch it out in case the DB server
blows up.

I want something automatic. Can anyone suggest what's worked well for them?

-KF

Report · May 16, 2006

Ken

I am not sure that you will be able to achieve this is classic ASP as it was
somewhat limited in grabbing exception errors. Tiy will need to have access
to this so that you could load in the connection strings.

--
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver

Valleybiz Internet Design
www.valleybiz.net

"Ken Fine" <kenfine@u.washington.edu> wrote in message
news:e4di8b$t33$1@forums.macromedia.com...
> SQL Server 2005 has a very nice feature called database mirroring that
> keeps two databases on two boxes in sync. Seamless failover to the
> secondary server is built into the .NET data provider:
> http://msdn2.microsoft.com/en-us/library/5h52hef8.aspx
>
> This is a neat trick. I need to be able to do something similar for my
> Classic ASP applications.
>
> The typical method for DB failover seems to be to store a connection
> string in global.asa or somesuch and manually switch it out in case the DB
> server blows up.
>
> I want something automatic. Can anyone suggest what's worked well for
> them?
>
> -KF
>
>

Report · May 17, 2006

From our friends at MSFT, they offer this solution:

To detect a Database is available, you may just open a connection to it and
catch possible error. For example:

Con.Open "Provider=SQLOLEDB; Data
Source=localhost;database=northwind;integrated security=SSPI"

If Err.Number <> 0 Then
..
Else
..

I'll give this a shot.

-KF

"Paul Whitham ACE" <design@valleybiz.net> wrote in message
news:e4dvk1$ena$1@forums.macromedia.com...
> Ken
>
> I am not sure that you will be able to achieve this is classic ASP as it
> was somewhat limited in grabbing exception errors. Tiy will need to have
> access to this so that you could load in the connection strings.
>
> --
> Paul Whitham
> Certified Dreamweaver MX2004 Professional
> Adobe Community Expert - Dreamweaver
>
> Valleybiz Internet Design
> www.valleybiz.net
>
> "Ken Fine" <kenfine@u.washington.edu> wrote in message
> news:e4di8b$t33$1@forums.macromedia.com...
>> SQL Server 2005 has a very nice feature called database mirroring that
>> keeps two databases on two boxes in sync. Seamless failover to the
>> secondary server is built into the .NET data provider:
>> http://msdn2.microsoft.com/en-us/library/5h52hef8.aspx
>>
>> This is a neat trick. I need to be able to do something similar for my
>> Classic ASP applications.
>>
>> The typical method for DB failover seems to be to store a connection
>> string in global.asa or somesuch and manually switch it out in case the
>> DB server blows up.
>>
>> I want something automatic. Can anyone suggest what's worked well for
>> them?
>>
>> -KF
>>
>>
>
>