Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Blastrix
Posting Yak Master
208 Posts |
 Posted - 2003-02-22 : 19:51:10
|
| We are currently in the process of changing our database server to cope with an increased amount of usage, and to implement another server in case of failure. The idea right now is to run a cluster with two SQL Servers running Enterprise Edition, against a 100GB disk array. Is there anything I need to look out for or change in my connectivity code, or the way I interact with the database, since the system is clustered?Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-24 : 18:22:52
|
| You should not have to change any code in order to access a database that is on a clustered server. We did not have to. |
 |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2003-02-24 : 18:44:09
|
| You may need to look at how your applications are connecting to the database. If I recall with our cluster, the machine has a machinename, and the "cluster" has a name. So, that might change your connection strings unless you are using IP's.Example:Machine: SQLServerPCCluster: SQLClusterOur connection string had to look at the Cluster name, so that in the event of failover, the other PC in the cluster would become "SQLCluster" and thus the applications keep running.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
|
|
|
|
|
|
Working With Clustered Servers