Shame on you VMware! Shame on you!


VMware, I am not impressed.

Guess the release date of SQL Server 2008 R2 SP1 for me, will ya?

I’ll give you a hint… Since it has only just been approved for use with vSphere 5.1, you’d hazard a guess recently, right?

Wrong!

SQL 2008 R2 SP1 was released in 11th July 2011. Date approved by VMware: 10th September 2012 (vSphere 5.1 release date).

Come on VMware… seriously? 14 months to approve a SQL service pack? That’s a joke.

I recently found out our administrators had applied SP1 to our SQL 2008 R2 servers earlier this year, when I tried to raise a support call and it was pointed out we were actually outside the VMware matrix.

I had to uninstall SP1 (thank you Microsoft for including this feature in SQL 2008 R2!) to get us back in line with the VMware compatibility matrix. The uninstall went quite smoothly (thank you again Microsoft) but that’s not really the point is it…

I’m running vSphere 5 Update 1 but I cannot apply SQL 2008 R2 SP1 or even SP2 because VMware are being slack!

Someone needs to up their game or loosen the compatibility matrix.

Advertisements

2 responses to “Shame on you VMware! Shame on you!

    • Hey Dave, That made me laugh… I take your point… don’t worry I am pretty loose, especially on weekends, but upgrading is not the point.

      The point is, VMware are not looking after those customers that cannot upgrade.

      There are a number of reasons why typically large enterprise organisations cannot immediately upgrade to vCenter 5.1. The organisation needs to do sufficient lifecycle testing with the new VMware components, i.e. building an vSphere 5.1 environment which replicates production, which can be tested with all their Tier 1 applications.

      Additionally vCenter 5.1 has its own requirements: upgrading to vCenter 5.1 forces an upgrade of: vCloud Director 5.1, Site Recovery Manager to 5.1, vShield Manager\vCloud Networking and security to 5.1, which triggers an upgrade of vShield Endpoint on all VMs… you get the idea and all of these trigger an upgrade of ESXi to 5.1. So upgrading to vCenter 5.1 is not a small task.

      Another good example of people who cannot just upgrade, are VCE customers who have vBlock’s and are locked into the VCE compatibility matrix to get seamless support.

      VCE validates and regression tests every component of the vBlock (UCS blades, EMC storage, Nexus switches, vSphere), so their customers do not have too. It takes a huge burden off their customers, as we know that VCE have stress tested and validated the individual components far better than we ever could. The downside is we have to wait a couple of months after every release for the VCE matrix to be updated.

      There is a good link here explaining it – http://kendrickcoleman.com/index.php/Tech-Blog/bringing-the-vce-goods-certification-matrix.html

      An even after the matrix is released, the individual components still have to be upgraded. Each datacentre takes at least 2 weekends to upgrade and a hell of a lot of planning with business owners and change management.

      Not easy and having just upgraded to vSphere 5 Update 1 we won’t be upgrading our environment any time soon.

      Hence my lack of looseness!

      Gareth

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s