 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers |
Webmaster Forum / ASP / Database Access / August 2007database connection issue
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 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) [quoted text clipped - 5 lines] > 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 Yes to both questions. I was able to connect to the Failover server, when it was used as the primary server. Also, I believe the documentation shows Failover Partner as 2 words, not 1. > BigSam wrote on Thu, 2 Aug 2007 09:48:05 -0700: > [quoted text clipped - 16 lines] > > Dan 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 >> 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 [quoted text clipped - 7 lines] >>> 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 I found the problem - it was application related. I created a simple web page that built a grid view with a Button click event. I used a text box to modify the connection string, which proved we were using the correct connection string. Since it wasn't the connection string I moved on - I used SQL Profiler to see what the application was doing & isolated the issue to the application. Thanks for your interest. BigSam > BigSam wrote on Fri, 3 Aug 2007 08:26:03 -0700: > [quoted text clipped - 35 lines] > > >> Dan |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.