SQL Server in a clustered environment: Running edition upgrade on one of the nodes of SQL Server cluster is sufficient. This node can be either active or passive, and the engine does not bring the resources offline during the Edition Upgrade. After the edition upgrade it is required to either restart the SQL Server instance or failover to a different node.

Microsoft does support "multi-site clusters", which basically allows failover clusters to be extended across geographically dispersed locations. Multi-site clusters rely on 3rd party replication solutions from storage array vendors and software host based replication solutions to keep the data in sync across sites. http://www.microsoft.com/windowsserver2008/en/us/failover-clustering-multisite.as

Although it's not best practice to place a ldf or mdf in the root of a drive ir can happen. As the permissions for the administrators and service account get removed the cluster service throws a hissy fit if the ldf or mdf is in the root of a cluster resource disk. It's not easy to fix either as if you don't fix the file permissions the drive goes offline again.
I have to question the wisdom of r

Failover Clustering can protect against disk failure if you replace the physical disk resource with a replicated volume resource from a 3rd party ISV (SteelEye DataKeeper or DoubleTake GeoCluster) or array based replication solution (EMC, IBM, ect). This solution gives you all of the benefits of clustering as well protection against disk failures.This article walks you through the steps of creat

If you're running SQL 2005 in a failover cluster configuration and you can't get the SQL Server Configuration Manager to list the certificate in the drop-down box where it should be here are some tips.
Ensure that the certificate was created with the FQDN of the virtual/cluster name.Follow the steps in "To provision (install) a certificate on the server" above to navigate to the certificate and

This applies to SQL 2005 for sure, but I have yet to test it on SQL 2008.
If you're running SQL 2005 in a failover cluster configuration and you can't get the SQL Server Configuration Manager to list the certificate in the drop-down box where it should be here are some tips.
Ensure that the certificate was created with the FQDN of the virtual/cluster name.
Follow the steps in "To provisi

If you're not sure what sort of a certificate to request a "Web Server" certificate will get you what you need. Just be sure to set the name to the FQDN like it says and if you're running a cluster be sure to use the virtual/cluster FQDN. If you happen to be running a SQL 2005 cluster with a SQL Server service account that is a domain account but isn't a local admin you will need to take additiona

When using the IP="ip address,Network Name" the Network Name part is the name of the network in the cluster networks NOT the Windows Network interface name.
If you do not not specify the correct network name according to the Cluster setup, then it will fail with a "network name not found" error.