我们使用 SourceSafe 6.0d 并且有一个大约 1.6GB 的数据库。我们还没有遇到任何问题,目前也没有更改源代码控制程序的计划,但是 SourceSafe 数据库在成为问题之前能有多大?
谢谢
我们使用 SourceSafe 6.0d 并且有一个大约 1.6GB 的数据库。我们还没有遇到任何问题,目前也没有更改源代码控制程序的计划,但是 SourceSafe 数据库在成为问题之前能有多大?
谢谢
我的 VSS 问题从低至 1.5-2.0 gigs 开始。
The meta-answer is, don't use it. VSS is far inferior to a half-dozen alternatives that you have at your fingertips. Part of source control is supposed to be ensuring the integrity of your repository. If one of the fundamental assumptions of your source control tool is that you never know when it will start degrading data integrity, then you have a tool that invalidates its own purpose.
I have not seen a professional software house using VSS in almost a decade.
1个字节!
:-)
对不起,伙计,你让我失望了。
Do you run the built-in ssarchive utility to make backups? If so, 2GB is the maximum size that can be restored. (http://social.msdn.microsoft.com/Forums/en-US/vssourcecontrol/thread/6e01e116-06fe-4621-abd9-ceb8e349f884/)
NOTE: the ssarchive program won't tell you this; it's just that if you try to restore a DB over 2GB, it will fail. Beware! All these guys who are telling you that they are running fine with larger DB are either using another archive program, or they haven't tested the restore feature.
我实际上运行了一个大约 40 gig 的 vss db。我不推荐它,但它是可能的。真的,你放得越大,你就越是在玩火。我听说过数据库损坏的情况,源代码管理中的项目无法恢复。我肯定会每天备份它并开始寻求更改源代码控制系统。处于失败时他们打电话给他们的那个人的位置上,我可以告诉你,当你意识到它可能会失败并且永远不会回来时,它真的会开始变得有压力。
考虑到 SourceSafe 可以自行产生的问题数量,我会说大小必须在“磁盘上存在”类别中才能产生问题。
我已经管理过两倍大小的 VSS 数据库。只要您对运行Analyze保持警惕,就可以了。
Sourcesafe 建议 3-5G 并带有“永远不要超过 13G”。
然而,在实践中,我们的超过 20G 并且似乎运行良好。
你得到的越大,Analyze 会发现越来越多的问题,包括丢失的文件等。
编辑:这是官方用词: http: //msdn.microsoft.com/en-us/library/bb509342 (VS.80).aspx
I have found that Analyze/Fix starts getting annoyingly slow at around 2G on a reasonably powerful server. We run Analyze once per month on databases that are used by 20 or so developers. The utility finds occasional fixes to perform, but actual use has been basically problem free for years at my workplace.
The main thing according to Microsoft is make sure you never run out of disk space, whatever the size of the database.
http://msdn.microsoft.com/en-us/library/bb509342(VS.80).aspx
quote: Do not allow Visual SourceSafe or the Analyze tool to run out of disk space while running. Running out of disk space in the middle of a complex operation can create serious database corruption