> We are moving to SQL2k5 & attempting to utilize mirrored databases. I
> gave a connection string to our developers to use in the ASP (classic)
> pages:
> "Provider=SQLNCLI;Server=10.0.0.1;Failover Partner=10.0.0.2;Initial
> Catalog=dbName;UID=SQL User Name;Pwd=Password;"
> When the database is Principal on the Server, the application connects,
> but it does not connect when the Principal is on the Failover Partner.
> I think there is a problem with the connection string, but I don't know
> what. Any help is appreciated.

> Thanks

"Daniel Crichton" wrote:

> BigSam wrote on Fri, 3 Aug 2007 08:26:03 -0700:
>
> > Yes to both questions. I was able to connect to the Failover server,
> > when it was used as the primary server.
>
> Have you tried since making it the failover server though? Just in case the
> Surface Area configuration has changed prevently connections being made.
>
> > Also, I believe the documentation shows Failover Partner as 2 words,
> > not 1.
>
> It does, but also notice that for some connection strings with other
> providers it is a single word. I suggested it merely in case there was a
> typo in the Native Client documentation.
>
> Dan
>
> > "Daniel Crichton" wrote:
>
> >> BigSam wrote on Thu, 2 Aug 2007 09:48:05 -0700:
>
> >>> We are moving to SQL2k5 & attempting to utilize mirrored databases.
> >>> I gave a connection string to our developers to use in the ASP
> >>> (classic)
> >>> pages:
> >>> "Provider=SQLNCLI;Server=10.0.0.1;Failover Partner=10.0.0.2;Initial
> >>> Catalog=dbName;UID=SQL User Name;Pwd=Password;"
> >>> When the database is Principal on the Server, the application
> >>> connects, but it does not connect when the Principal is on the
> >>> Failover Partner.
> >>> I think there is a problem with the connection string, but I don't
> >>> know what. Any help is appreciated.
>
> >>> Thanks
>
>
> >> Have you tried FailoverPartner (one word)?
>
> >> Have you tried connecting directly to the failover IP when it is the
> >> Principal?
>
> >> Dan
>
>
>