Obliterate function is very very slow

Sourav · Post by **Sourav** » Tue Oct 25, 2005 12:13 pm

Hi,

We started using SourceGear Vault and moved all our VSS databases into Source Gear Vault.

Now the sourcegear vault database size is 37 GB. When we backup this database we end up with a backup file that is only 20 GB.

I found that there are lot of files that are deleted but yet to be Obliterated.

The Obliterate function does not work as expected. It is very very slow and takes hours and hang up the Admin tool and the Vault server slows down. I looked in the TaskManager the sqlServer process takes 20-30 % CPU but is doing a lots of IO read/write.

It seems like that during Obliterate operation the database is doing table scans and thats the reason the SQL Server slows down.

I searched the forum and it seems like Obliterate is a slow operation but I did'nt find any technical reason for it.

In my case when I tried to delete a folder which had a lot of sub folders under it the obliterate function took approx. 4 hours before it showed the confirmation dialog that asks whether I want to delete this files or not !!!

Another issue is dependencies, when I am trying to obliterate for some of the files it says that there is dependency and I need to remove that before I can obliterate this file but it does not say what it is. Is there a way to force obliterate?

Overall I am still trying to get rid of the files that are already delete and bring down the size of the database but was not able obliterate any files yet.

Any help is appreciated.

lbauer · Post by **lbauer** » Wed Oct 26, 2005 10:11 am

Obliterate takes a long time because we want to make sure it's done correctly. We are working on making improvements in obliterate for Vault 4.0 so that it will still be correct, but faster.

Usually when you can't obliterate due to dependencies, it means you're trying to obliterate a trunk without first obliterating its branches. But if you try to obliterate the branches along with the trunk, you get a message with an empty branches list.

We're working to fix that, too.

The best bet is to first obliterate any branches, then obliterate the trunk.

Sourav · Post by **Sourav** » Wed Oct 26, 2005 10:22 am

Thanks for the reply.

In one of the repository I have only two folders that I need to obliterate. When I am trying to obliterate any one of the folder it throws the message that I need to delete the branch first. Now I cannot delete either of this folders since both are displaying the same message.

Is there a workaround to clean these folders? Also whats the planned release date for Vault 4.0