Import keeps failing

[Dalek]

Hi,

I have a VSS database of about 800Mb with multiple shared projects some of which contain file branches and most of which contain quite a few labels. I've tried several times to import it using the vault tool on a 2.66GHz P4 with 1.6Gb or RAM and two fast Maxtor Hard Disks one with the SourceSafe db on it and the other (C:\) running Vault, SQL Server and the Vault import tool. I've been through all the recommended timeout settings in machine.config and the two Vault config files and I've purged all the deleted files out of my SS database for good measure. Despite all this, each time I try to import the process just seems to give up the ghost at some point with the current import file name freezing and the processor usage dropping to zero. The point at which this happens depends on the size of the SS database, with the full one it usually doesn't get through the pre-scan, with a paired down version with all the archive stuff purged out it gets to the file import stage before giving up. In this situation the rest of the machine is fine and operates as normal but the import tool is effectively frozen and all you can do is cancel the import.

So, of course I'm wondering what I'm doing wrong - obviously I haven't tried the import on two networked machines as recommended but before I embark on that I wanted to check if there's any other timeout thing (or other setting) that could be causing this to happen. I've looked at the processor load during the import and seen that it has a cycle of a burst of high activity followed by a quiet period, the problem is that at some point for my import it goes into the quiet period an never comes out again. I've enclosed the logs from my latest attempt (the one with most stuff purged from the db) in case that will indicate anything useful.

Any ideas?

[jeremy_sg]

It sounds like your import tool is running out of memory. If you watch the memory usage, I'm guessing that the import hangs when it gets around 1 Gig of memory usage. We discovered a way to reduce memory usage of the import tool for people that have lots of shares, but the discovery came days after 2.0 was released, and it's a pretty major change that would need to be tested fully before we include it in a new release. For now, if you would like to give it a try, email me, and I'll send it to you.

Your other option is to archive as much of the history in the VSS database as you can stand and try again.