I hear that VSS 2005 uses SQL-Server...
Moderator: SourceGear
-
duncab
I hear that VSS 2005 uses SQL-Server...
How will Vault distinguish itself from what's scheduled to be released with VS 2005 Team services or VSS 2005? I hear that VSS2005 will use SQL-Server 2005.
That's a big topic, one which I cannot fully cover right now. Here are a few thoughts:
With the introduction of Visual Studio 2005, Microsoft will have two source control tools.
-- One is still SourceSafe (aka VSS).
-- The other is Team Foundation System (aka TFS), a completely new product.
The new VSS is not really all that new. There will be a number of incremental improvements, but the core is fundamentally the same. It is still SourceSafe. It does not use SQL Server for storage. It does not have atomic checkins. It remains to be seen whether the SourceSafe team has fixed the stability problems.
In contrast, TFS is completely new. It is not based on any other tool, but was built from the ground-up, from scratch.
Comparing Vault to TFS is a bit tricky right now, since TFS won't be shipping for another year or so. However, there are a few things which are starting to become clear:
1. TFS will be a lot more expensive than Vault. Fundamentally, TFS is positioned to compete with very high-end products like ClearCase. It's going to cost a lot of money, and current MSDN Universal subscribers are not going to just get it for free with their subscription.
2. The transition from SourceSafe to TFS will not be as painless as the transition from SourceSafe to Vault. For example, TFS does not support Share or Pin. If these features are important for you, the transition to TFS will be more difficult.
As I said in a recent post on my weblog:
With the introduction of Visual Studio 2005, Microsoft will have two source control tools.
-- One is still SourceSafe (aka VSS).
-- The other is Team Foundation System (aka TFS), a completely new product.
The new VSS is not really all that new. There will be a number of incremental improvements, but the core is fundamentally the same. It is still SourceSafe. It does not use SQL Server for storage. It does not have atomic checkins. It remains to be seen whether the SourceSafe team has fixed the stability problems.
In contrast, TFS is completely new. It is not based on any other tool, but was built from the ground-up, from scratch.
Comparing Vault to TFS is a bit tricky right now, since TFS won't be shipping for another year or so. However, there are a few things which are starting to become clear:
1. TFS will be a lot more expensive than Vault. Fundamentally, TFS is positioned to compete with very high-end products like ClearCase. It's going to cost a lot of money, and current MSDN Universal subscribers are not going to just get it for free with their subscription.
2. The transition from SourceSafe to TFS will not be as painless as the transition from SourceSafe to Vault. For example, TFS does not support Share or Pin. If these features are important for you, the transition to TFS will be more difficult.
As I said in a recent post on my weblog:
I predict that TFS will be an outstanding product and a big success, but there will continue to be a lot of developers who want other choices, for one reason or another.
Eric Sink
Software Craftsman
SourceGear
Software Craftsman
SourceGear