Database Verification Script for Identity Manager Installation

Background: Identity Manager fails to install or upgrade successfully

VMware Identity Manager can fail to upgrade or install successfully if certain best practices are not followed, or database configurations are incorrect. On both Windows or Linux, symptoms can include seeing the connector activation screen after completing the installer for the full version of identity manager. On Linux, you will not be able to proceed to the database configuration screen. 

Database setup failure is often the root cause of this issue. In order to ensure the database is configured correctly, use the script provided in this article to verify database configuration details and provide expected results. 

Customer Impact

The failure to upgrade or install successfully can result in the inability to use or configure VMware Identity Manager. In order to mitigate these issues, follow the best practices outlined in this article and use the database verification script as needed to ensure correct configurations. 

Please keep the following guidelines in mind when running the configurator wizard on Linux:

  • Do not run the VMware Identity Manager configurator wizard with the IP address.
  • Do not run the VMware Identity Manager configurator wizard with the short host name (should be a fully qualified host name). 

Note: The best practices in this article extend to all supported versions of On-Premises VMware Identity manager installs. 


Use the script provided if you encounter a failure to upgrade or install successfully, or as needed to ensure correct configurations. Run the script with the same user planning to connect to the database through VMware Identity Manager and replace the "DatabaseName" with the actual name. 


// Check if user is DB owner. Return true = 1



// Make sure user is not sysadmin. Should return false = 0



// check if SaaS schema exists, should be not null



// check schema owner, should be user provided to installer



// check if SaaS is user default schema, should return SaaS



// check DB collation, should return Latin1_General_CS_AS


SELECT DATABASEPROPERTYEX(‘DatabaseName', 'Collation') AS Collation


// check if read committed snapshot is on, should return true = 1

SELECT is_read_committed_snapshot_on FROM sys.databases WHERE name=‘DatabaseName'

Have more questions? Submit a request


Article is closed for comments.