Prepare DBs for vSphere 5.1 installation or upgrade – Part 1

Quick guide how to prepare databases for vSphere 5.1 deployment. Part one focus on Microsoft SQL database which is most common database platform for vSphere deployments. Before vSphere 5.1 installation or upgrade three databases have to be ready:

  • VMware vSphere 5.1 Single Sign-On
  • VMware vSphere vCenter server
  • VMware Update Manager

vSphere 5.1 vCenter server DB

Create  VMware vSphere vCenter database and user.
  • Execute below script from MSSQL management studio. Change path to DB files, user names and passwords accordingly


Configure MS SQL ODBC on vCenter server
  • On vCenter server go to menu start –> Administrative tools –> Data sources
  • From a Data sources window click on System DSN tab and ADD button,  choose SQL server from data sources driver

  • Specify ODBC name, description, MS SQL server name or IP address
  • I next window select authentication modes , provide username and password
  • Choose default DB
  • Test connectivity

VMware vSphere Update Manager (VUM)

Create database
  • Execute below SQL script in MSSQL management studio tool


  • Verify DB user rights and make sure that the database user has either a sysadmin server role or the db_owner fixed database role on the Update Manager database and the MSDB database.
  • Go to SQL management studio, Log in to MSSQL server where VUM DB was created.
  • Go to Security – Logins – vmuser – properties, click on server role and mark sysadmin server role

  • click on user mapping – click VUM — from DB role membership click on db_owner

Create ODBC for VMware Update Manager
 VMware update Manager support only 32 bit ODBC
  • start 32bit ODBC from path c:\Windows\SysWOW64\odbcad32.exe
  • Add new ODBC in system DSN tab
  • Scroll down and click on SQL Server
  • Provide name, description and sql server IP address or name
  • choose authentication type and provide DB credentials
  • choose default DB and finish
  • test database connectivity

VMware vSphere 5.1 Single Sign-On database

Create DB and table space RSA_INDEX and RSA_DATA
  • Execute script rsaIMSLiteMssqlSetupTablespaces.sql. The script is included in the vCenter Server installer download package, at vCenter Server Installation directory\Single Sign On\DBScripts\SSOServer\schema\mssql. You can run this script prior to the installation, or during the installation, when you are prompted by the installer. make sure you provided path to database files by change a section CHANGE_ME in a scrip.


  •  To create these users, run the script rsaIMSLiteDBNameSetupUsers.sql. The script is included in the vCenter Server installer download package. \Single Sign On\DBScripts\SSOServer\schema\mssql . Make sure you changed password for both users by changing CHANGE DBA PASSWORD and CHANGE USER PASSWORD in script.


  • Verify if users appeared in system

  • Done, DB ready for SSO deployment.
Error 29119, Required Tablespaces missing during the installation of vCenter Single Sign On. Make sure that DB was created using  script from rsaIMSLiteMssqlSetupTablespaces.sql file.

Artur Krzywdzinski

Artur is Consulting Architect at Nutanix. He has been using, designing and deploying VMware based solutions since 2005 and Microsoft since 2012. He specialize in designing and implementing private and hybrid cloud solution based on VMware and Microsoft software stacks, datacenter migrations and transformation, disaster avoidance. Artur holds VMware Certified Design Expert certification (VCDX #077).

  • Ramana

    Thanks Arthur for article. It has very good information.

    • artur_ka

      Thanks, soon I will post second (oracle) and maybe third (DB2) part of a series

  • Oulas

    I have made RSA DB with rsaIMSLiteMssqlSetupTablespaces.sql and users with the rsaIMSLiteDBNameSetupUsers.sql without getting any errors during execution but I still get the Error 29119. I have already created VCDB database using the pethod in the vmwares quide, that also requires to excecute about 20 scripts that this is not instructed in your documentation. What else should I check not receiving Error 29119? (I still do not have create VUM DB? I use the installation with the simple sign on.

    • artur_ka

      hard to say what was went wrong during SSO DB creation, give a second try. In regards of VCDB creation, there is no need to execute 20 scripts, all what you need is empty DB, DB user with proper rights. Installationmigration wizard will createimport DB tables into empty DB.
      Is good to have separate DB for VUM but this decision is based on size of your environment, typically if you have 8 or more hosts you should split VCDB and VUM DB into two separate DB’s.

      • Oulas

        Thank a lot for this quick answer. I ll try to recreate again the RSA database.

  • Oulas

    Do I need to create an ODBC DSN for RSA database? Thanks a lot!

  • MS

    The article is very usefull for SQL Server;
    Waiting for Oracle Steps for vCenter SSO Database creation

    • artur_ka

      Thanks, I have to install Oracle first 🙂 which’s not as easy as MSSQL installation,

  • Koutsi

    Could you comment on the compatibility of BL460c G1 with ESXi 5.1? Thanks!

  • Sunil Pyyan

    Hi.. I will try this and let you know

  • Fred Witteman

    Do you also have scripts for Maintenance tasks ?
    1. Maintenance Plan Cleanup History Files
    2. Maintenance Plan Backup Database vcdb and vumdb
    3. Maintenance Plan Backup Transaction Log

    • Nope. I don’t have but it is a good idea for blog post. I will post them soon.

  • xdaudaudau


    you wrote “vSphere 5.1 vCetner.”

    it should be “vSphere 5.1 vCenter.” 🙂