Michael Salish wrote: > The net effect is that when you check in a 20-40MB 'file' the SCS can > take a very long time to determine the differences. So make one tiny > change and you are looking at a time-wasting process to check it back > in.
I run my repository on a 350 MHz Win2k server, and there's no appreciable time (seconds at most) for committing my files. I don't use DDBs, though, I use file system-based projects. A 40 MB single DDB file may take a bit longer; that's true. > We use Visual Source Safe and it also has it's own issues. Tell me about it :) VSS is known to be prone to data loss, mainly because it's not a client-server architecture. The program used on the user's computer accesses the repository on the server directly (through network share access). One hiccup in the file write and the repository needs to be repaired. This is especially problematic with off-site VPN access. > Bottom line is the risk of loss goes up and the time is increased by > using a single DDB. I'm using CVSNT and never had any data loss caused by working with the repository. But you are completely right in that DDBs don't make sense for using with a version control system, whichever it is. Gerhard ____________________________________________________________ You are subscribed to the PEDA discussion forum To Post messages: mailto:[email protected] Unsubscribe and Other Options: http://techservinc.com/mailman/listinfo/peda_techservinc.com Browse or Search Old Archives (2001-2004): http://www.mail-archive.com/[email protected] Browse or Search Current Archives (2004-Current): http://www.mail-archive.com/[email protected]
