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.”
In fact, under Services, there is a “SQL Server Agent” that will not start.
Windows Event logging responds with this one:
And in the Microsoft SQL Server Management Studio, the SQL Server Agent does not show up (as it does in other Editions).
I tried to figure out why the vCenter server would not manage the historic data. Finally I decided to upgrade to the Standard Edition. Many thanks to my employer for paying my MSDN subscription!
Upgrading from Microsoft SQL Server 2008 R2 Express Edition to Standard Edition is a supported upgrade. Here is the tutorial.
1. First step, have Installation media and a license key available.
2. Mount the installation media and start setup.
3. Choose Media and start Edition Upgrade.
4. At First the Setup Support Rules performs a few tests that must be met.
6. Accept the Licence terms.
7. In the Select Instance Windows, no change and Next.
8. Next window Edition Upgrade Rules, should also report Passed.
9. And at last in the Ready to upgrade edition window, press Upgrade to start the upgrade process. The whole process takes only a few moments.
10. And the last window displays the result.
11. The first action is to start the service SQL Server Agent. Unfortunately, the service will not start. Microsoft KB 955763 provides a solution.
12. The solution is to change the account in the Logon Tab. This one will not work:
13. After changing to this one, the service will start. (I know standard Administrator is not a good idea, but this is homelab…).
14. The SQL Server Agent now starts.
16. The Microsoft SQL Server Management Studio, now shows the SQL Agent. Bonus, all Jobs are still there! In case the jobs Past Day stats rollup, Past week stats rollup and Past Month stats rollup are not present, VMware KB1004382 describes how to configure those jobs.
Well, I hope you enjoyed reading this blogpost. If you have any questions or remarks, please respond.
Update 15-05-2011: There is at leat one caveat after upgrading to the Standard Edition, please read this post.