|
| | | Forum Newbie
Group: Forum Members
Last Login: 3/11/2008 6:41:57 PM
Posts: 9, Visits: 17 |
| | When using a MS SQL server back end in a ultra high availability enviroment, using an alias for your SQL server with the cliconfg tool is essential to having multiple back end clusters. If one cluster fails, changing the value of the IP address with a script quickly re-routes traffic to another cluster. However, it wasn't until I added a matching entry in my host file that the installer was able to see the database. A test connection with the ODBC manager uses the value in cliconfg fine, but the installer does not seem to honor that. It appears that the installer is trying to use DNS to resolve the name of the SQL server prior to using it. I haven't run an wireshark trace on the nic yet to confirm this, but it seems likely. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 3/11/2008 6:41:57 PM
Posts: 9, Visits: 17 |
| | I also confirmed that after the install, if I remove the entry in the host files, the services fail to start. Looks like the services themselves are dependant on DNS. I found a dbconfig.exe in the utilities directory, but I can't seem to discover where it writes the name of the SQL server for the services to use. It doesn't appear to be stored in the registry or in a config file that I can see. |
| |
|
|