Posts Tagged ‘vi3.5’
Why not VirtualCenter with SQL 2005 Express?
As of VirtualCenter 2.5 (VC) MSDE was replaced by SQL 2005 Express as the default installation database. This post explores the idea of running small and medium business (SMB) VMware virtual infrastructure (VI) environments with the free SQL 2005 Express version instead of a fully licensed instance of SQL 2005/2000.
To start with VMware’s VI3.5 and VC2.5 Installation Guide states:
The Microsoft SQL Server 2005 Express database package is installed and configured when you select Microsoft SQL Server 2005 Express as your database during VirtualCenter installation or upgrade. This is shown in Installing VMware Infrastructure Management Software. No additional configuration is required.
If Microsoft SQL Server 2005 Express is already installed, review the required database patches specified in Table 2-1. If you do not prepare your database correctly, the VirtualCenter installer might display error and warning messages.See www.microsoft.com/sql/editions/express/default.mspx.
Note: Microsoft SQL Server 2005 Express is intended to be used for small deployments of up to 5 hosts and 50 virtual machines.
5 ESX hosts and 50 VMs is definitely enough support for most small business deployments. Frankly, with modern hardware pricing the 50 VM limit will be reached before ever deploying 5 ESX hosts. 16 guests on a host is a common scenario these days which, if you do the math, creates a 3 host ESX Cluster.
So why would a company that does not expect to grow it’s number of VMs beyond 50 not use SQL 2005 Express? Here’s the 2 best reasons I could think of, and then a counter argument for each. Read the rest of this entry »
VMware Virtual Infrastructure to be renamed vSphere
VMTN moderator and Roundtable podcast regular Jason Boche and virtualization bloggers Rick Schere and Scott Lowe are reporting that VMware will be changing the name of their flagship enterprise Virtual Infrastructure products from VI 3.5 to vSphere. Following mostly the same individuals’ tweets on Twitter I learned that the new name was decided via a vote by VMware employees. It’s unclear to me at this time when the name change will officially take place, but I imagine it will coincide with the availability of the next software release.
First some quotes from the other guys, and then my first impression. Read the rest of this entry »










