I would like to open this topic up to others as I have heard some Pro's and Con's with SQL as a VM on either Hyper-V or VMware. Some have told me that they would never run SQL as a virtual machine.
Now if you double the CPU specs for the SQL VM and memory then on the DSS side like what David did add the Write Back option this should almost be enough. But maybe David you might want to use MPIO (you will need to 2 NICs) and possibly a RAID 10 for the dedicated SQL VM (SAS or SSD's). Not sure but increasing some of the Target values like below but test first not in a production system.
Adjust the target values as follows:
1. From the console, press CTRL+ALT+W,
2. Select Tuning options -> iSCSI daemon options -> Target options,
3. Select the target in question,
4. change the MaxRecvDataSegmentLength and MaxXmitDataSegmentLength values to the
maximal required data size (check w/ the initiator to match).
Anyone else that have some ideas as I would like to add this in our blog.open-e.com ??
Thanks David for posting this as this has been in my head as well and I dont have SQL to test (too many other systems testing now).
Reply With Quote