Quote:
You can trade off between performance and robustness with a choice of backends - although I'm using the allegedly less robust BerkeleyDB backend and haven't had any problem so far.


We opted for the FSFS backend -- we're on Windows, and I didn't want to worry about BDB versions.

We do a hot snapshot of the repositories every night (we have 3), and they're backed up with everything else.

Quote:
Access methods are flexible, with built in ssh tunneling if needed, and even a web front end (which I haven't used yet).


We've got ours hosted on Apache2, and we allow external HTTPS access as well. This is useful for when people are working from home (like me, now, for instance), and for the guys in our Indian office.

The built-in WebDAV interface allows you to access the repository directly from Word, e.g. We've turned on auto-versioning so that our documentation people don't have to worry about it.

WebSVN is a very nice web-based interface.

Quote:
For Windows users, TortoiseSVN is a brilliant front end (shell namespace extension).


I'll second that -- if you've only just started using it, check out the options available when you right-drag a version-controlled resource somewhere else.

We're also using SubverRRSed (from an hourly cron job, rather than a commit hook), which generates an RSS feed showing what's been checked in, and by who.
_________________________
-- roger