[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

781.0. "How to access Dual Sql Servers' DB from one client." by NNTPD::"liudavid@mail.dec.com" (David Liu ) Thu May 01 1997 15:53

Hi, Our customer want the following. 

A windows 95 /NT client access 2 DB located  on a pair of  Dual SQL Clustered
Server (With Digital Cluster V1.1)  [With one DB located on one failover group
with Server A as Primary & 2nd DB located on the other failover group with
Server B as Primary ] 

How can that Windows 95/NT client access those DB ?
  Can it access both DB by using the Cluster Alias (With Name-Pipe)?   or
  Can it access both DB by specifiy 2 different IP address ( With TCPIP
Winsock)?
 OR any other suggestion ?

Thanks !
David
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
781.1Dual pipes works.MBSVAX::SLOANJust Another Manic MondayThu May 01 1997 21:1611
    Both databases can be accessed using ISQL/w on the client.  You will
    have to configure an alternate pipe to access the second database, as
    detailed in the V1.1 Administrator guide - Using the SQL Client
    Configuration Utility.  I have been able to get dual pipes working on 
    Windows NT Workstation V3.51 and V4.0.  I have, so far, not been able to 
    get dual pipe access working on Windows 95. 
    
    Hth,
    
    
    /Shaun
781.2By Chances !!!NNTPD::"Eddy.Wang@hgo.mts.dec.com"HKTSFri May 02 1997 09:5322
We have been tested both Win95 and Winnt client under dual SQL environment
using 
advanced setting and found that all databases can be seen now.  This is a good

news to us.

However, we've encountered client needs to initiate the connection again
rather
than just a refresh.  This only happens sometimes; I would say by chances! 
This
apply on both Win95 and Winnt clients.

Pls kindly advice.

Rgds,
Eddy

:>


[Posted by WWW Notes gateway]
781.3LJSRV1::GOODMANMon May 05 1997 11:224
During a manual failover client connections should be severed. Manual failover is an administrative procedure.
So, this should not be a problem. SQL server failover time with V1.1 has\
increased.  The FMSQL.dll has more work to do with dual sql primarys support. This is why before dual sql support
the client appeared to stay connected.
781.4Client need initiate is abnormal !?NNTPD::"Eddy.Wang@hgo.mts.dec.com"HKTSMon May 05 1997 14:4618
So, if clients need to initiate again for a continuous connection
can we say this is abnormal??  My clients are using only ISQL which 
is the client kit from SQL v6.5 server CD; which I believe is stated 
to be supported in dual SQL.

As I mentioned before, the "initiate again" is only by chances.  
Sometimes we don't sometimes we do need.

Pls advice.


Rgds,
Eddy.

:}

[Posted by WWW Notes gateway]
781.5Need to reconnect is normalDECWET::CAPPELLOFMy other brain is a polymerMon May 05 1997 19:392
    Clients almost ALWAYS need to initiate the DB connection again after
    failover.  The cluster documentation talks about this.  It is normal.