I received multiple questions around this so decided to ask around internally. I managed to get ahold of the VMware Update Manager (aka VUM) Product Manager and after exchanging a couple of emails this is the outcome:
VMware vSphere Compatibility Matrixes
Table 13 on page 14 of the above linked document states that VUM doesn’t support MS SQL 2008 Standard. This is however untrue and should be considered as a document bug. It is supported and the document will be modified soon to reflect these changes.
Ask them also why they require a x64 os but then require a x32 odbc driver? doesn’t make sense when this release was supposed to be x64. I hope they resolve that in the next verson.
How about SQL 2008 R2? We are migrating off 2008 and onto SQL 2008 R2.
Little confused on the odbc connection for update manager. Like anon comments above update manager requires a 32 bit odbc connection on a 64 bit OS. However reading the vCenter server setup guide it states on page 114:
vCenter Update Manager requires a supported database. The database requirements are the same as vCenter Server, except that DB2 is not supported. You can use a supported database that is configured to work with vCenter Update Manager, or you can install the Microsoft SQL Server 2005 Express database that is bundled with vCenter Update Manager. vCenter Update Manager can use the same database as vCenter Server, but
VMware recommends that you have separate databases for vCenter Server and vCenter Update Manager.
I assume the odbc connection can be 64 bit. When did this change?