Board index » off-topic » Replacing SourceSafe with StarTeam - is it viable for me?

Replacing SourceSafe with StarTeam - is it viable for me?


2005-02-28 11:08:53 AM
off-topic4
I connect to a company's SourceSafe database via VPN, but due to
performance problems we are looking for alternatives. I initially
suggested SourceOffsite by SourceGear, but as a result they are
investigating migrating the VSS database to SourceGear Vault. I know
nothing about this repository, and would be quite keen for them to
migrate to StarTeam instead.
I own two StarTeam Standard editions (v5.4 and v6.0), which came with
my Delphi 8 and Delphi 2005 SKUs, and am wondering whether these can be
utilized to help to sell them on the idea. Considering I already use a
named user license to connect to a local StarTeam server (or will do
once I can get it working again :-( ), can this named user license be
used to connect to another StarTeam server? Or is it against the
license to have one named user license registered with two seperate
servers. Alternatively, can a StarTeam 5.4 client license be used to
connect to a StarTeam 6 or 2005 repository?
Also, what is the performance of the client like when using it over the
internet. Is it acceptable, or quite sluggish? The last thing I want is
to suggest a solution which had comparable performance issues.
--
Cheers,
David Clegg
XXXX@XXXXX.COM
Vote 1 cc.borland.com/codecentral/ccweb.exe/listing :-)
Now supports Google Groups searching with Dyna-extend(tm) technology!
QualityCentral. The best way to bug Borland about bugs.
qc.borland.com
"Oh, people can come up with statistics to prove anything, Kent. 14% of
people know that." - Homer Simpson
 
 

Re:Replacing SourceSafe with StarTeam - is it viable for me?

David Clegg wrote:
Quote
I own two StarTeam Standard editions (v5.4 and v6.0), which came with
my Delphi 8 and Delphi 2005 SKUs, and am wondering whether these can
be utilized to help to sell them on the idea.
Possibly. StarTeam can wrap a VSS repository without converting it to
native StarTeam format. How complicated this is depends a lot on how
complicated your VSS DB is; you'll need to create users (not
necessarily licensed users, just user accounts as placeholders) in
StarTeam for each VSS user, and you probably won't be happy with the
results of the wrap and eventual go-native process if:
o Your VSS project structure is poor -- the structure will be imported
as-is, of course.
o You use heavy branching and pinning in VSS.
o You use renaming a lot in VSS.
See the StarTeam manuals for more info.
Quote
Considering I already
use a named user license to connect to a local StarTeam server (or
will do once I can get it working again :-( ), can this named user
license be used to connect to another StarTeam server?
Named user licenses are server-based, so no, but this doesn't apply to
wrapping another SC system such as VSS.
Quote
Or is it
against the license to have one named user license registered with
two seperate servers.
Right. It would be a license violation to use the same user license
with two separate servers. The user license is the *only* license for
the server, after all.
Quote
Alternatively, can a StarTeam 5.4 client
license be used to connect to a StarTeam 6 or 2005 repository?
As of StarTeam 2005 (I think) there *is no* client license, and the
StarTeam 2005 client can connect to a StarTeam 6 server (but not 5.4, I
think).
Quote
Also, what is the performance of the client like when using it over
the internet. Is it acceptable, or quite sluggish? The last thing I
want is to suggest a solution which had comparable performance issues.
I've only used the web client heavily, and it's acceptable. I would
*presume* that the GUI client is as good or better than the web client,
but it's just a guess.
-Craig
--
Craig Stuntz [TeamB] ?Vertex Systems Corp. ?Columbus, OH
Delphi/InterBase Weblog : blogs.teamb.com/craigstuntz
IB 6 versions prior to 6.0.1.6 are pre-release and may corrupt
your DBs! Open Edition users, get 6.0.1.6 from mers.com
 

Re:Replacing SourceSafe with StarTeam - is it viable for me?

David Clegg wrote:
Quote
I own two StarTeam Standard editions (v5.4 and v6.0), which came
with my Delphi 8 and Delphi 2005 SKUs
FWIW, I'm pretty sure the Standard licenses don't include VSS
wrapping. Or is it importing to a native data store?
-Brion
 

{smallsort}

Re:Replacing SourceSafe with StarTeam - is it viable for me?

Brion L. Webster wrote:
Quote
FWIW, I'm pretty sure the Standard licenses don't include VSS
wrapping.
I know it's technically possible, as I used to do it. Not sure if it's
against the licence though. If it is, disregard my first sentance. :-)
--
Cheers,
David Clegg
XXXX@XXXXX.COM
Vote 1 cc.borland.com/codecentral/ccweb.exe/listing :-)
Now supports Google Groups searching with Dyna-extend(tm) technology!
QualityCentral. The best way to bug Borland about bugs.
qc.borland.com
"You've tried and failed. The lesson here is, never try again." - Homer
Simpson
 

Re:Replacing SourceSafe with StarTeam - is it viable for me?

Craig Stuntz [TeamB] wrote:
Quote
Possibly. StarTeam can wrap a VSS repository without converting it to
native StarTeam format.
Yeah, but then I'd be stuck with many of the performance limitations
that I currently have with VSS. And like you said in an earlier thread
"it would be like swatting a fly with a sledgehammer".
Sounds like it's going to be a moot point anyway, as it looks like the
company has already started migrating to a SourceGear Vault repository.
--
Cheers,
David Clegg
XXXX@XXXXX.COM
Vote 1 cc.borland.com/codecentral/ccweb.exe/listing :-)
Now supports Google Groups searching with Dyna-extend(tm) technology!
QualityCentral. The best way to bug Borland about bugs.
qc.borland.com
"If the Bible has taught us nothing else, and it hasn't, its that girls
should stick to girl's sports, such as hot oil wrestling foxy boxy and
such and such" - Homer Simpson
 

Re:Replacing SourceSafe with StarTeam - is it viable for me?

David Clegg wrote:
Quote
Brion L. Webster wrote:

>FWIW, I'm pretty sure the Standard licenses don't include VSS
>wrapping.

I know it's technically possible, as I used to do it. Not sure if
it's against the licence though. If it is, disregard my first
sentance. :-)
Maybe it's the migration part then. I remember being irritated
when I first installed 5.6.
-Brion