I think many have tried doing this, but few have succeeded. No commercial
application (specifically) helps with this. VSS needs a single database and
coordinating the database changes that happen between two databases just
really isn't feasible.

Joe

Hi,

mirroring is just a simple copy, however it is not possible to work on
the original and cloned database and merge them together.In my last
company we have tried several things to improve performance, security
and maintainability:

-Split up the database, as each site was working on independant modules.
For the daily build, one database was synced back using robocopy to the
main site and used for the build. However, there were tasks where one
had to work on the other databse which still had the bad performance.
This was a good solution for the security issue, however, it was a
maintainance nightmare keeping the syncs and the build schedule and in
shape.

-Use SourceGear SourceOffsite.
http://www.sourcegear.com/sos/index.asp  This is a nice  tool that lets
you work with a SourceSafe vault via the network with really good
performance. Actually this worked so well, that we abandoned the two
database aproach and used it at the remote sites. Maintainance was good
then ( a single vault), however we were sitll affected by the database
server being offline

-Use a client server toll, such as Perforce
http://www.perforce.com
or SourceGear vault.
http://www.sourcegear.com/vault/index.asp
We finally moved to perforce (vault wasn't availbale at that time)
because of the performance improvements and the capabilities to build
mirrored servers at the remote sites that could syncronize themselves
with the main vault.

Another soulution to the security/uptime aspcet would be, to let a
extern provider host your source safe vault. Those providers can usually
make a 24/7 guarantee and connection to te vault can be done with
SourceOffsite with a good performance

HTH,
Andy