当前位置：文江博客话题详情

TFS 业务案例

发布于 2024-11-17 08:21:01 字数 112 浏览 0 评论 0原文

我正在尝试构建一个从 VSS 迁移到 TFS 的业务案例，特别是我正在寻求澄清不这样做的成本和风险。

您认为可以为公司节省超过 1 万英镑的 3-4 个杀手锏是什么？

非常感谢。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

飘逸的'云 2024-11-24 08:21:01

“您认为可以为公司节省超过 1 万英镑的 3-4 个杀手锏是什么？”

最好的答案之一是此处。本白皮书详细介绍了所有优势。

以下是 pdf 文件中的一个结果：

性能、可靠性和可扩展性
由 SQL Server 2008 团队支持
Foundation Server 的优势在于
的性能和可扩展性
行业领先，企业级
数据库服务器。对于小团队来说
不需要成熟的力量
SQL Server 安装，安装在
像 Windows7 这样的客户端操作系统并使用
SQL Server Express 提供相同的
轻量级的强大发动机
包裹。这提供了关键之一
VSS 从未有过的好处 – 您可以
从小事做起，随着时间的推移而成长。
从 SQL Server Express 升级到
SQL Server 的完整版本如下
简单如备份和恢复。其他
SQL Server 的优点包括
动态扩展存储的能力
根据需要，更快的读/写，以及
集群作为容错的一部分
解决方案。
紧密结合
Team Foundation Server 和 Visual
Studio为用户提供熟悉的
和有效的源头控制
开发环境。通常
Visual SourceSafe 开发人员必须
在外部打开 VSS 用户界面
Visual Studio 完成源码
控制任务。因为团队
基础服务器集成
Visual Studio，几乎所有选项
关于源代码和工作项目
可以直接通过
Visual Studio（一些管理
需要完成的功能
通过全功能命令
线）。
一个容易产生影响的问题
VSS安装是4GB
建议限制。哪些球队是
接近或超过此限制
它往往会发现腐败问题
他们的源代码需要修复。
从备份恢复此数据是
经常很困难，因为团队
必须依赖系统管理员
恢复文件共享。又来了，
Team Foundation Server 发挥优势
SQL Server 的强大功能。 SQL服务器
具有内置的数据保护功能
腐败，但如果发生这种情况，
通过 SQL Server 恢复
备份。 SQL Server 允许许多
不同的数据保护方案
增量和完整备份到日志
运输和镜像这一切
提供可靠的机制
保护您的数据。
安全
在 VSS 中，
安全性仅限于三种设置
– 管理、读/写和读。正在申请
文件级别的安全设置
是可能的，但经验是
远非易事。主要缺点是
这种安全感在于它是一个全部
或者没有任何类型的安全——如果你
可以写入你可以做的文件
任何你想要的东西。和
因为一切都存储在
文件共享，任何有权访问的人
文件共享可以简单地将其全部删除。
虽然您的源代码具有精细的安全性
代码可能并不重要，团队
Foundation Server 确实提供了它。
除了能够控制
文件级别的安全性，团队可以
还支持特定场景，例如
就像让开发人员检查一个
文件但不签入。这是
在许多情况下都很方便，例如同伴
审查和外包开发。
而且，由于它存储在 SQL Server 中，
丢失所有源代码，因为
删除的情况将永远不会再发生。

"What would your top 3-4 killer reasons that would save a company more than £10k?"

One of the best answers out there is here. This whitepaper goes over, in detail, all of the advantages.

Here is an exert from the pdf file:

Performance, Reliability and Scalability
Backed by SQL Server 2008, Team
Foundation Server benefits from the
performance and scalability of an
industry leading, enterprise class
database server. For small teams that
don’t need the power of a full-fledged
SQL Server installation, installing on
a client OS like Windows7 and using
SQL Server Express provides the same
powerful engine in a lightweight
package. This provides one of the key
benefits that VSS never had – you can
start small and grow over time.
Upgrading from SQL Server Express to
the full version of SQL Server is as
simple as a backup and restore. Other
benefits of SQL Server include the
ability to dynamically expand storage
as needed, faster read/writes, and
clustering as part of a fault tolerant
solution.
The tight integration of
Team Foundation Server and Visual
Studio provide users with a familiar
and effective source controlled
development environment. Typically
Visual SourceSafe developers had to
open the VSS user interface outside of
Visual Studio to accomplish source
control tasks. Because of the Team
Foundation Server integration with
Visual Studio, virtually every option
regarding source code and work items
can be accomplished directly through
Visual Studio (some administrative
features need to be accomplished
through the full-featured command
line).
One issue that tends to effect
VSS installations is the 4GB
recommended limit. Teams which are
close to this limit or have exceeded
it tend to find corruption issues in
their source code requiring repair.
Restoring this data from a backup is
frequently difficult because teams
have to rely on system administrators
to restore the file share. Here again,
Team Foundation Server takes advantage
of the power of SQL Server. SQL Server
has built-in protection against data
corruption but, if that occurs, it can
be restored through a SQL Server
backup. SQL Server allows for many
different data protection schemes from
incremental and full back ups to log
shipping and mirroring which all
provide reliable mechanisms for
protecting your data.
Security
In VSS,
security is limited to three settings
– Admin, Read/Write and Read. Applying
security settings at the file level
was possible, but the experience was
far from easy. The major drawback to
this security was that it was an all
or nothing type of security – if you
could write to the file you could do
anything you wanted with it. And
because everything was stored on a
file share, anyone with access to the
file share could simply delete it all.
While granular security of your source
code may not be critical, Team
Foundation Server does provide it.
Along with being able to control
security at the file level, teams can
also support specific scenarios such
as letting a developer check out a
file but not check it in. This is
handy in many situations such as peer
reviews and outsourced development.
And, since it is stored in SQL Server,
losing all of your source code because
of a delete will never happen again.