How risky is that?

From Dan Gardner, "Risk":
 
"Thus if an independent thinker really wishes to form entirely independent judgements about the risks we face in daily life, or even just those we hear about in the news, he or she will have to obtain multiple university degrees, quit his or her job, and do absolutely nothing but read about all the ways he or she may die until he or she actually is dead"

SQL 2008 failover clustering

A few things:
 
  • Unlike SQL 2000, SQL 2008 standard will let you create a 2-node failover cluster; SQL Enterprise allows a 16-node cluster.
  • The minimum number of partitions/ LUNs needed for SQL 2008 seems to be 3; Quorum, DTC (both created for Windows cluster) and the data store (our old 2K3 clusters didn’t need a seperate DTC partition)
  • Despite following the "Advanced/Enterprise Installation" section of this document that my colleague found- http://download.microsoft.com/download/6/9/D/69D1FEA7-5B42-437A-B3BA-A4AD13E34EF6/SQLServer2008FailoverCluster.docx– clustering didn’t work properly; the Analysis service wasn’t failing over. So… we ended up removing the faulty node and adding it as an additional node as per later on in this document.
  • The last step of adding a node might result in this interesting "error":
  • I don’t know if MS have noticed, but this is a statement, not a question- it’s an instruction to install SQL 2008 SP1. So why the "Yes/ No" option? (also, it would have been more helpful if MS had just said"Install SQL 2008 SP1" than drilling down to the gritty version numbers).

Update- GUID schmuid

Thanks to Guy Teverovsky- http://blogs.microsoft.co.il/blogs/guyt/archive/2009/04/09/hotfix-id-what-does-this-guid-stand-for.aspx– I can now find out which hotfixes I need to install.
 
I have to say MS were particularly unhelpful in regard to this issue; I couldn’t even log a support call without an KB article number. If I knew which KB article the GUID referred to, I wouldn’t be phoning you…
 
  • Further update! Even more irritatingly, the missing updates had been bundled into other updates that were installed. So why the cluster validation tool couldn’t have just figured that one out by itself I don’t know… but I forcibly installed them, and the cluster now validates successfully…

GUID schmuid

When asking SQL 2008 to validate our new cluster (active/ passive), it rather unhelpfully said that the cluster failed because the software levels are not in synch, and then just listed a big bunch of GUIDS:
 
{D6705815…
{D2F3957E…
 
And so on- I think you get the message. Before trying to hunt out these "Hotfix IDs" anywhere, try using Add/Remove programs to look for incompatabilties; in this case, I think all these hotfixes could well be related to the Office 2007 compatibility pack (installing it on the other node and running Windows Updates has certainly got rid of a few of these out-of-synch GUIDs.