Recently, I was asked to investigate a vCenter Server 5.0 having issues with its database. As a result, the “VMware Virtual Center Server” service stopped and vSphere Clients were losing connectivity.
The vCenter Server was running on a Microsoft SQL Server 2008 R2 Express Edition. Although not very recommended for production environments, see also my previous post, for small environments it will do. This instance worked well for over one year, unfortunately, the Server Statistics settings had recently been set to level 3, resulting in fast growing database- and transaction log files. Resetting the Server Statistics to the original settings (level 1) did not quite solve the situation.
The first idea was to purge old data from the database, as is clearly explained in KB 1025914.
So after downloading the VCDB_Purge_MSSQL.zip script and adjusting the following variables: