Any suggestions for me on shared files imports?

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
jdavidi
Posts: 48
Joined: Thu Jul 06, 2006 1:29 pm

Any suggestions for me on shared files imports?

Post by jdavidi » Fri Aug 04, 2006 8:35 am

Using VSS Import 3.5.0...

For about 3 years now, we've shared files in VSS when we split the tree for new versions, and have typically branched the files on an as-needed basis. When we convert everything to Vault, we're considering doing away with sharing altogether and making use of the Merge tools when code changes have to go into multiple versions.

Having read the Tips for Successful imports here:
http://support.sourcegear.com/viewtopic.php?t=8 ,

it looks like breaking down our projects into sizeable "archive chunks" will be the way we'll want to approach the import of our (on average) 6 GB VSS databases.

This brings me to a number of questions:

If we end up wanting to keep shares:

1a) When you break up projects into "archive chunks" that have sharing information, is this sharing information lost upon importing into Vault, since not every project that a file is shared with will be part of the same archive?

1b) If the sharing information is indeed lost (at least upon the initial archive import), are they somehow re-established as you import other archives?

If we end up not caring about shares:

2) Is it any more efficient (speed-wise, data integrity-wise, space-wise) to break all shares in VSS prior to archiving/importing?

Clear as mud what I'm asking, right? :)

Thanks much!

--jdavidi

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Aug 04, 2006 2:29 pm

When you break up projects into "archive chunks" that have sharing information, is this sharing information lost upon importing into Vault, since not every project that a file is shared with will be part of the same archive?
Yes. However we have a special build of the import tool that can re-establish shares after the import if you've imported the VSS database a few projects at a time instead of the entire database. This works if the project structure is the same in Vault as it was in VSS.

I don't believe it would save any import time if you branched your shares. The VSS import tool recreates VSS history, and branching just adds to folder history.

Email me if you'd like the debug import tool.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply