pre-import steps

[Don Robinson]

Our firm has just purchased Vault after a lengthy review process. One VSS repository is on my home office system, and needs to be moved to our new sql server. I can't find enough information on the steps (maybe I should look harder?). Here is what I think I need to do.

1// Analyze the current VSS repository (which I normally do every couple of weeks)

2// roll up the VSS repository and transfer it to a workstation located in our physical office (to avoid internet traffic issues or bottlenecks)

3// unroll the VSS repository to a temporary system

4// run the VSS import client

Any advice (or pointers to documentation) would be most welcome.

[jeremy_sg]

That seems about right. Make sure that VSS 6.0c plus the hotfix is installed on the machine that will be running the import. You can read the Tips for a Successful VSS Import at:

http://support.sourcegear.com/viewtopic.php?t=8

[Don Robinson]

Ah yes - the hotfix. I'd forgotten that.
Thanks very much!

[clint alexander]

Just in case..

Also, just wondering whether it would be simplest to 1. ask the development team to fully 'check-in' each repositories files, 2. freeze development, 3. move these files inside the LAN on which the sql/.net vault server resides (for bandwidth/speed reasons that you point out) and then 4. pool the source code and other files (for 1 *or more* applications) inside the appropriate repository (e.g., see the "Forestry" repository I made on our server), with the logical folder breakdowns for the different apps. What I'm thinking of is not using the import tool at all, but just FRESHLY adding the desired code bases into Vault instead.

It sounds like the downside is that you lose all the history info in VSS. However, I (as a neophyte to source control) am probably missing something really fundamental here..