SourceGear Support

Also Beth, I was looking through the SQL Server profiling that I currently have constantly running - which is a small drain on resources, I just profile stored procedure calls, and login and logout - and this set of statements is repeated so many times it may be the majority of the profile over 24 h...

Items 1-3 should only affect each individual user's client. Are they all logging in at exactly the same time? Is it just during that first login that the server CPU goes to 100%? Well (1) clearly effects everyone because the one user takes up all the CPU and so anything else requested grinds to a h...

1) To help with starting up the client, go to Vault Tools - Options - Network Settings and turn off the option "Request Database Delta on Repository Cache Miss." 2) Have the users try changing the setting on 'Use Expect: 100-Continue headers'. Let me know if there is any different with th...

On what exact actions are you getting the performance issues on. Is it possibly just when clients start up, or is it during Gets or check ins? Start up, gets and Check Ins. The latter has gone from a few seconds to 30 seconds. Which version of Vault are you using? As per signature - 5.0.3 Are you u...

Please DO log a feature request for this.

This error was recorded in sgvault.log when performing a merge whilst attempting to list the merge versions. The Vault Client was in a wait state until the error was reported in sgvault.log at which time the Client was no longer in a wait state but no other user interface feedback occurred. This hap...

You can move the repository by one of two methods. 1) Use our Export/Import tool to export everything out and import it to the new Vault server. 2) Restore a backup of the entire database to a SQL Server (or instance), then install a 2nd Vault server to pick up that restored database. Next delete a...

since you mentioned performance in another post, I'm assuming that's why you are removing a repository, and the SQL maintenance will help that. Thats correct. But the user capitulated late yesterday and is now going to remove all the binary objects that were coincident with slower performance in Va...

How large was your database prior to the delete and obliterates? 18 GB. We have not yet deleted objects. It will happen next week. Expect about 3 GB to be freed. I'm planning for it now. Have we discussed the performance issue with you previously? If so, can you point me to the thread where that di...

We are going to remove 90% of the objects and maybe 95% of the disk used in one repository. After that is done, and the objects have been obliterated is there anything else required to restore the performance of the database to a state as if those deleted objects had never been added? This includes ...

Thanks Beth.

And will the original database be as if the deleted repository had never been there? Like indexes, or deleted objects, or...?

...and can the 2nd instance be on the same SQL Server?

Is there anything to beware of? IIS?

How do you refer to the 2nd instance from the Client? - its usually the machine name.

Another possible cause... At the end of last week we started using Test Complete with Vault. This seems to be coincident with the login issue. The Test Complete interface to Vault is named "VS .Net 2003". I therefore presume its a classic client interface. Do you know if this is the case? ...

Some more statistics are attached to this post - formatting is retained: Repository Statistics.txt The last Repository - VLF - has grown to this enormous size in the last 2 months, coincident with the slowdown in performance of other repositories. e.g. Check In. Maybe this is a separate issue to the...

Hi,

Could you tell us what the steps are to move an entire repository out to another SQL Server instance so that the original database performs as if that removed repository never existed?

thanks