Geek Answers Handbook

How big can the Sourcesafe database be before the "problems"?

We use SourceSafe 6.0d and have a database of about 1.6 GB. We still had no problems, and now there are no plans to replace version control programs, but how big can the SourceSafe database be before it becomes a problem?

thanks

+4
source share
8 answers

Do you run the ssarchive built-in backup utility? If so, 2 GB is the maximum size that can be recovered. ( http://social.msdn.microsoft.com/Forums/en-US/vssourcecontrol/thread/6e01e116-06fe-4621-abd9-ceb8e349f884/ )

NOTE: ssarchive will not tell you this; it's just that if you try to restore a database of more than 2 GB, it will fail. Caution! All these guys who tell you that they work fine with a larger database, either use a different archive program, or did not test the restore function.

+2
source

My problems with VSS start with 1.5-2.0 gigs.

Meta response: do not use it. VSS is far inferior to the half-dozen alternatives that you have at your fingertips. It is assumed that part of the source control should ensure the integrity of your repository. If one of the fundamental assumptions of your source control tool is that you never know when it will begin to degrade data integrity, then you have a tool that robs it of its own purpose.

I have not seen professional home software using VSS in almost ten years.

+9
source

1 byte!

:-)

Sorry dude you set me up.

+8
source

I really run vss db, which was about 40 gigs. I do not recommend, but it is possible. In fact, the more you let it go, the more you play with fire. I heard cases when db is damaged, and the elements in the original control were unrecoverable. I would definitely support it on a daily basis and start looking for changes to version control systems. Being in the position of the guy they call when he fails, I can tell you that he will really start to feel stress when you realize that he can just go down and never come back.

+2
source

Given the number of problems that SourceSafe can generate on its own, I would say that the size should be in the "Present on disk" category so that it can create problems.

+2
source

I used VSS DB twice as much. As long as you are vigilant about doing Analysis , you should be fine.

+1
source

Sourcesafe recommends using 3-5G with "never switch to 13G."

In practice, however, ours is over 20G and seems to work fine.

The more you get, more and more problems will be detected in the analysis, including lost files, etc.

EDIT: Here is the official word: http://msdn.microsoft.com/en-us/library/bb509342(VS.80).aspx

+1
source

I found that Analyze / Fix starts to annoyingly slow down by about 2G on a fairly powerful server. We run Analyse once a month in databases that are used by approximately 20 developers. The utility detects occasional corrections for execution, but the actual use for many years was practically independent of my workplace.

Most importantly, according to Microsoft, make sure you never run out of disk space, regardless of the size of the database.

http://msdn.microsoft.com/en-us/library/bb509342(VS.80).aspx

Quote: Do not let Visual SourceSafe or the analysis tool work while you work. Running disk space in the middle of a complex operation can seriously damage the database.

+1
source

More articles:


All Articles