4

I am now in the process of building SQL Server 2008 Enterprise failover cluster for use with 3rd party server monitoring application (which also do some OLAP analysis for trends).

Since this project will be using SQL Server 2008 Enterprise over Windows Server 2008 failover cluster, I wonder do I have to separate the DB engine instance and the OLAP component or just make it as single instance altogether ?

yes I'll use the Physical RDM capabilities so that i can use the built in EMC CX Snapview for data replication to my DR site because the two VMs will be deployed across two different locations

I am looking for any specific tweaking for the VMware: maybe enabling the MMU and using VMXNet 3 and Paravirtual for the boot device ?

or within SQL Server eg. large pagefile in RAM, etc...

Any other suggestion and idea in tweaking and performance tuning of this failover clustering on top of VMware ESX will be greatly appreciated.

Thanks,

AWT

Senior Systems Engineer
  • 1,275
  • 2
  • 33
  • 62

1 Answers1

1

Wmware has a good guide for deploying MSSQL cluster on ESX. It includes many best practices for configuration.

sky100
  • 504
  • 2
  • 3
  • now i decided to re-think and draw again from scratch as previously it was my idea at 1 AM, so it seems that Failover clustering on top of VMware HA is too complex to implement and slight downtime ~ 5 mins during the failback/server restart is acceptable for me, therefore I have now decided to go with SQL Server 2008 Mirroring HA (see the attached). http://i54.tinypic.com/m80aj9.jpg--> the latest diagram. – Senior Systems Engineer Jun 01 '11 at 04:19