In the meantime, for those not yet on Vault 10.1 or those on Vault 10.1 with a large cache, there is a workaround that will help with this particular performance problem until it is resolved:
Note, these instructions on the workaround will need to be performed one at a time per repository. To start, determine the unique ID for the repository for the GUI Client. After logging into a query tool within SQL Server, run the following SQL command: "SELECT uniquerepid, name FROM sgvault.dbo.tblrepositories;"
For each Vault GUI client encountering the issue:
- Log into a Vault client, and make a list of known working folders. Note, the Vault Command Line Client has a LISTWORKINGFOLDERS command that reports assigned working folders
- After the list has been noted, remove all working folders for the repository
- Shut down all Vault Clients
- Using the information from the SQL query above, open Windows' File Explorer, and go to %LOCALAPPDATA%\SourceGear\VaultPro_1\Client\<Repository-GUID-from-above>\<user-login>\
- Delete the CacheMember_PendingServerNamespaceChanges and CacheMember_WorkingFolderAssignments within that directory
- Start up the Vault Client.
If the GUI Client start up performance has not been resolved there may be other issues. Customers with Vault maintenance are encouraged to contact SourceGear Technical support vial email to <support AT sourcegear DOT com>"