This issue is resolved in vCenter Server 5.1. You can download the latest release, available at
VMware Downloads.
To work around this issue, delete the primary key constraint and create a clustered index:
- Connect to the vCenter Server database using SQL Management studio.
- Take a backup of the existing vCenter Server database. For more information, see Backing up the vCenter Server database running on Microsoft SQL or SQL Express server (2012138).
- Execute this SQL statement against the vCenter Server database:
IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[VPX_VM_FLE_FILE_INFO]') AND name = N'PK_FLE_FILE_INFO')
ALTER TABLE [dbo].[VPX_VM_FLE_FILE_INFO] DROP CONSTRAINT [PK_FLE_FILE_INFO]
GO
- Execute this SQL statement against the vCenter Server database:
CREATE CLUSTERED INDEX [VPX_VM_FLE_FILE_INFO_ID_KEY_VAL] ON [dbo].[VPX_VM_FLE_FILE_INFO]
(
[VM_ID] ASC,
[KEY_VAL] ASC
)
GO
Note: If you implement this workaround, duplicate information related to virtual machine snapshots may exist in the vCenter Server database for a very short period of time. This causes inaccurate values to be displayed for Space Used and Snapshot Space under the Storage Views in the vSphere Client until the snapshot is deleted.