Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Migrating the vCenter Server database from SQL Express to full SQL Server (1028601)

Last Updated: 3/20/2024Categories: How toTotal Views: 4423Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides steps to migrate a VMware vCenter Server database from a SQL Express server to a full SQL Server instance

Notes:

When performing an in place upgrade of SQL Express to SQL Server the roll up jobs will need to be created.

You may need to migrate from SQL Express to SQL Server if you are close to or exceeding 5 hosts, 50 virtual machines, or 4 GB database size. (In Microsoft SQL Express 2008 and newer, the maximum database size is increased to 10 GB.)

Resolution

To migrate the vCenter Server database from an SQL Express instance to full SQL Server:

Note: Ensure that you are using the dbo schema and not custom schemas in your vCenter Server database.

Stop the VirtualCenter Server service.

Take a complete backup of the vCenter Server database. Do not skip this step.

Stop the vCenter Server database on the SQL Express server.

Copy the backed up database to the full SQL Server host.

Create a new database on the full SQL Server.

Restore the backed up SQL Express vCenter Server database to the newly created database. To ensure a proper restore, navigate to Options and click Overwrite existing database with replace.

Notes:

The instructions above also apply when full SQL Server is installed locally on the vCenter Server Windows host. SQL Express 2005 is upgraded to SQL Server 2008 after you have created the new 2008 database and restored the SQL Express 2005 database to the SQL 2008 Server.

If the new instance of full SQL Server is installed locally for the database migration, the vCenter Service's SQL Server Instance dependency may need to be recreated or modified.

You must remove and recreate the system DSN so that it uses the SQL Native Client 10.0/11.0 driver. Download the x86 for vCenter Server 4.0 and earlier, and x64 for vCenter Server 4.1 and later.

Note: The preceding links were correct as of October 24, 2014. If you find a link is broken, provide a feedback and a VMware employee will update the link.

Ensure the DSN connects to the newly created database on SQL 2008 Server. For vCenter Server 4.1 and later, ensure a 64-bit DSN is created for the ODBC connection.

For vCenter Server 5.1, the Single Sign-On (SSO) database may also have to be migrated.

Configure the vCenter Server account that connects to the database as the dbo user of the MSDB system database.

Update the ODBC connection on vCenter Server.

Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see Microsoft Knowledge Base article 136393.

To update the ODBC connection settings for vCenter Server 4.x/5.x:

Click Start > Run, type regedit, and click OK. The Registry Editor window opens.

Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > VMware, Inc > VMware VirtualCenter.

Modify the key DbInstanceName and remove the current Value data. Do not delete this key.

Modify the key DbServerType and change the Value data from Bundled to Custom.

Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > VMware, Inc > VMware VirtualCenter > DB.

If the ODBC connection name is changed, modify Key 1 with the name of the new ODBC connection.

Modify Key 4 and change the ODBC driver to the new driver.

Modify key 2 and add the vCenter Server user, for example sa.

To update the ODBC connection settings for vCenter Server 6.x:

Navigate to: C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx. (Default Path)

Take a backup copy of vpxd.cfg

Open the vpxd.cfg file in a text editor.

Locate the <DB> element and modify the value for <key_2> to reflect the new database user ID.

...
<DB>
<key_2>database_user_id</key2>
<key_3>*joqDY/eQvwyLBdLcXXJYZvDAd+FXYY8q7x///vhy4LE=</key_3>
</DB>
...

Note:-If you are using Windows Integrated Authentication to connect to the vCenter Server database, remove the value for <key_3>.

Save the vpxd.cfg file.

To change the database password stored in the registry(vpxd.cfg file in case of vCenter Server 6.x) and to allow the user to update the ODBC information without reinstalling vCenter Server.

Click Start > Run

Type cmd

Right-click on the Command prompt icon and select Run as Administrator.

Run this command:

C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe -p

Note: This is the default path to the vCenter Server installation directory. Change the path appropriately, if required.

Recreate the rollup jobs. For more information : Verifying jobs and stored procedures installed in vCenter Server 5.1, 5.5 and 6.x

Ensure that the vcdb.properties file found in below location reflects the new SQL database information, otherwise, change the URL manually to the new SQL Server address:

vCenter Server 5.x/4.x: C:\ProgramData\VMware\VMware VirtualCenter
vCenter Server 6.x: C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx

Example
vcdb.properties:
usevcdb=true
url=jdbc:sqlserver://<SQL_SERVER_NAME>;databaseName\=<VCDB>
username=username         ------------>(SQL Authentication account )
password=password          ------------>(SQL account password)
dbtype=mssql
driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

Note: If using vCenter Server 5.0 ensure that the database settings used by the Tomcat Server are updated.

Start the vCenter Server services.

If vCenter Server service has dependency on SQL Express follow the steps given below:

Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\vpxd.

Click the DependOnService column. The value of DependOnService lists all the services the vCenter Server depends on.

Delete the SQL Express service line.

Do similarly check for ControlSet001 and ControlSet002 folders.

Reboot the vCenter Server.

Ensure the SQL Express service was set to manual/disabled and stopped.

Start vCenter service.

Note: If you experience issues accessing the Storage View tab after the migration, see Accessing the Storage tab view in vCenter Server 5.0 fails with an internal error: com.vmware.vim.sms.fault.serviceInitializationException (2015180).

Note:If you are experiencing Error : vcdb.error.read.data Error while reading data from the vCenter Server database: Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections.

make sure while modifying the SQL DB access we follow the permissions as mentioned in https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.install.doc/GUID-B7C29C3F-1D15-47E2-AA79-DC4AB3DF546E.html

And Make sure Granting additional privileges to the vCenter Server database user using KBA https://kb.vmware.com/s/article/2114754

Related Information

For more information on migrating the Update Manager database, see the Migrating the Update Manager Data and Upgrading Update Manager on a Different Machine section of the vSphere Installation and Setup Guide.
Administrative credentials are required for Oracle and SQL Server databases when installing or upgrading vCenter Server
How to stop, start, or restart vCenter Server services
VMware VirtualCenter Server service does not start automatically after reboot
Upgrading VMware vCenter Server 4.0/4.1 fails with the error: Setup found that multiple schemas exist in the database
Cannot start the vCenter Server service after migrating the db to a new server
VMware vCenter Server fails to populate performance charts and displays an error message when using a custom JDBC SQL port
Verifying jobs and stored procedures in VMware vCenter Server 4.1.x
Verifying jobs and stored procedures installed in VMware vCenter Server 5.0
After migrating the vCenter Server database to a new host, the VMware VirtualCenter Management WebServices service does not function correctly
Accessing the Storage tab view in vCenter Server 5.0 fails with an internal error: com.vmware.vim.sms.fault.serviceInitializationException
Verifying jobs and stored procedures installed in vCenter Server 5.1, 5.5 and 6.x
Updating the vCenter Single Sign-On server database configuration
Migrar la base de datos de vCenter Server de SQL Express 2005 a SQL Server 2008
将 vCenter Server 数据库从 SQL Express 迁移到完整的 SQL Server
vCenter Server データベースを SQL Express から完全な SQL Server に移行する
Migrando o banco de dados do vCenter Server do SQL Express para o SQL Server completo
Moving the VMware vCenter Server 4.x/5.x/6.x SQL database

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
首次引导期间 vCenter Server Appliance 6.7 迁移失败 - vAPI Endpoint 服务首次引导失败 -“首次引导期间无法配置 vAPI Endpoint 服务 (Failed to configure vAPI Endpoint Service at the firstboot time)”-“本机平台错误 [代码: 5][在存储‘TRUSTED_ROOTS’上开始枚举失败 (Native platform error [code: 5][B (57128)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 5.5.x

Take Our Survey

Support Assistant