[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SourceSafe to SVN

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 22 Aug 2008 07:00:27 -0400

On Fri, Aug 22, 2008 at 00:33, kevin <kcocol_at_gmail.com> wrote:
> In SourceSafe (SS) we run daily jobs to ensure the DB is sound. If
> not, we can run jobs to correct. Does SVN require anything like this?

No, SVN doesn't have any such requirement.

You're lucky that the corruption you're getting is recoverable. When I
was dealing with VSS, we lost whole chunks of our repository with ho
hope of recovery.

> Can't the DB become corrupted? If so, is there a way to know
> proactively (AKA - before a user tries to grab a file for checkout)
> and tools to try and correct? Is the only remedy backup/restore in a
> corruption situation?

You should always have backups, as noted by others. But the odds of
you needing that back backup are the same as the odds that you won't
need a VSS backup - pretty small (outside hardware failure, which all
are equally vulnerable to).

Switch to SVN, drop the VSS mindset of lock-modify-unlock (which you
allude to above in saying "before a user tries to grab a file"), and
never look back. In 6 months, you'll be shaking your head wondering
why & how you tolerated that POS from MS for so long.

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-22 13:00:47 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.