Vault vs SOS 4.0

We currently use SOS 3.5 and I am trying to evaluate the benefits of moving to either SOS 4.0 or Vault 2.0.

 

It would be very beneficial if there were some sort of chart comparing features of the two products. [Hint, hint…]

If someone might be willing to create a summary that would be very helpful.

 

In the meantime, I have been browsing through product documentation for Vault (with which I am less familiar) and the new features and fixes in SOS 4.0.

 

One of the biggest problems I have is administration – I am constantly forgetting the admin passwords to the various VSS databases we have while trying to remember the steps to set up new databases etc. Another issue we have is the cloggy IDE integration that VS.NET has with source control in general. Finally, having cached login credentials is probably the biggest feature of SOS 4.0 that interests me. We’ve never had any corruption in VSS [knock on wood], so that is not a big issue to me.

 

This leaves me with a few questions (although I’d still love to see that feature comparison chart):

* Does Vault have the ability to cache login information so that users are not prompted multiple times when opening large VS.NET solutions?

* Are there plans to eventually have integrated Windows Authentication in either product?

* If I import, say, 10 different VSS databases into our Vault server, do I setup different user accounts for each database (even when they are the same user), or do I set up each user once and then configure which users have permissions for which databases?

* Are there any other time-saving features that make VS.NET developers more productive that exist in one product but not the other?

 

Thanks!

 

Luther

 

 

 

 

 

_____________________________________________________________
Luther Miller • Managing Architect • MCSD (.NET)
Softagon Corporation • www.softagon.com
1 Pier Ste 3 • San Francisco, CA 94111
(415)946-6113 • (510)387-3490 cell • (415)946-6101 fax