Some time ago, I wrote an article about upgrading a Microsoft SQL Server 2008 R2 Express edition to a full Standard Edition. Today I discovered that the transaction log of the vCenter Server database (in my homelab) has grown and needed some maintenance. VMware published KB 1003980 “Troubleshooting transaction logs on a Microsoft SQL database server” on this subject. However It is not my intention to go for a Simple recovery Model. So I decided to create a Maintenance Plan. After creating a Maintenance Plan, I discovered that it is not possible to modify an existing Maintenance Plan. There is an Modify option, but it just does not work.
I know, it is highly NOT recommended to run vCenter on a Microsoft SQL Server Express edition, even in test or development environments! So it is not difficult to understand that in my homelab vCenter ran on a Microsoft SQL Server 2008 R2 Express Edition…
And everything went well, until I noticed this message (probably after upgrading to vCenter 4.1)
I also discovered that vCenter had no performance Data older then one day. Searching VMware’s knowledge base, I found KB1004382. The KB states that: “This article does not apply to installations using Microsoft SQL Server 2005 Express. SQL Server Agent is not available in Microsoft SQL Server 2005 Express. Historic data is managed by the VirtualCenter Server service in this case.”