| 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 |
Hi, One of my Customers (Kelloggs in the UK) has Clusters for NT V1.0 acting as an Application and SQL server. We have set up the system to fail over SQL, and the application failover is controlled by a script . The client then connects to the working system to get the application and uses ODBC to access SQL server. The ODBC access to the cluster alias works fine on the LAN, but cannot be accessed over a TCP/IP routed network. This does not surprise me for Clusters V1.0, the question that I have is: Will 1.1 make it work ? and........ Can ODBC be set up to use TCP/IP ? If so how ? Could ODBC on the remote client be set up to access the SQL server via a Clusters 1.1 roaming IP address ? If so how ? As you may have guessed,I need help understanding the ODBC transport and server communications mechanism, so if the remote access propblem is not solved by V1.1 any input as to how it might be done would be useful. Thanks Colin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 712.1 | ODBC can use TCP/IP with V1.1 | MSE1::MASTRANGELO | Mon Mar 24 1997 09:55 | 31 | |
With V1.1 you can use ODBC to connect to a SQL Server database using
TCP/IP.
On the cluster:
Create your databases and enroll them for failover (follow the
instructions in the Administrator's guide).
Create an IP object specifying an IP address that you wish to use for
accessing your SQL Server databases (not one of the addresses of the
servers, a new address) and add the IP object to the group with
contains your SQL Server databases.
On the client:
Use the SQL Server Client Configuration Utility to create a server
connection. Go to the Advanced property page and create a new entry.
For Server, specify the name you wish the connection to be known as
(i.e. dbnameIP). For DLL Name, select TCP/IP Sockets. For Connection
String, specify the IP address you used for the IP object you dropped
into your SQL database group.
In Control Panel, use the ODBC applet to add a DSN (Data Source
Name). Specify whatever you like for the Data Source Name and
description. For Server, select the drop down listbox and the server
connection you created using the SQL Server Client Utility should
appear. Select it.
Your ODBC app should now be able to use this DSN to connect to the SQL
database on the cluster using TCP/IP Sockets.
| |||||
| 712.2 | Thanks | CHEFS::16.42.4.4::Colin | Confusion Reigns | Wed Mar 26 1997 05:24 | 5 |
Thanks, I'll now get them to upgrade to 1.1 Colin | |||||