VMware Update Manager vCenter. And click the green plus to create a new permission; Under Users and. VMware Infrastructure Update Manager.

It’s that time again (to bring up the age old topic of Microsoft SQL database permission requirements in order to install VMware vCenter Server). This brief article focuses on vCenter 5.0.

Permissions on the SQL side haven’t changed at all based on what was required in vSphere 4. However, the error displayed for lacking required permissions to the MSDB System database has. In fact, in my opinion it’s a tad misleading. To review, the vCenter database account being used to make the ODBC connection requires the db_owner role on the MSDB System database during the installation of vCenter Server. This facilitates the installation of SQL Agent jobs for vCenter statistic rollups. In the example below, I’m using SQL authentication with an account named vcenter. I purposely left out its required role on MSDB and you can see below the resulting error: The DB user entered does not have the required permissions needed to install and configure vCenter Server with the selected DB.

2.10 Example of Transmission Function Approximation. 2.9 The Function D (s) As An Approximation Function.

Please correct the following error(s): The database user ‘vcenter’ does not have the following privileges on the ‘vc50’ database: EXECUTE sp_add_category EXECUTE sp_add_job EXECUTE sp_add_jobschedule EXECUTE sp_add_jobserver EXECUTE sp_add_jobstep EXECUTE sp_delete_job EXECUTE sp_update_job SELECT syscategories SELECT sysjobs SELECT sysjobsteps Now what I think is misleading about the error thrown is that it’s pointing the finger at missing permissions on the vc50 database. This is incorrect. My vcenter SQL account has db_owner permissions on the vc50 vCenter database. The problem is actually lacking the temporary db_owner permissions on the MSDB System database at vCenter installation time as described earlier. The steps to rectify this situation are the same as before.

Grant the vcenter account the db_owner role for the MSDB System database, install vCenter, then revoke that role when vCenter installation is complete. While we’re on the subject, the installation of vCenter Update Manager 5.0 with a Microsoft SQL back end database also requires the ODBC connection account to temporarily have db_owner permissions on the MSDB System database. I do believe this is a new requirement in vSphere 5.0. If you’re going to install VUM, you might as well do that first before going through the process of revoking the db_owner role.

An example of where that role is added in SQL Server 2008 R2 Management Studio is shown below: • •. I think this should really be changed with vCenter and its frustrating VMware is not thinking with an enterprise mindset. This means you cannot have vCenter run in a corporate environment on a corporate SQL Server. No corporate DBA’s agree to give any application access to the MSDB system db on their corporate highly available super duper SQL envieonment This means you are forced to have a separate SQL server just for vC & VUM separate from the pure corporate database environment just for the necessary MSDB rights (even if it is just for installation). The access required is not for critical vCenter operation, only running stored procedures for stats roll ups. What VMware should do is warn that the SQL Agent jobs cannot be scheduled without MSDB access but allow the installation to complete.