Visual Source Safe Database
-
Early in the coming New Year, I will be setting up a new development sever that will replace an very old and tired one. One of the software components that must be moved is the MS Visual SourceSafe software and database. I know that I can install the VSS software on the new server, but I can not locate any type of utility that will 'move' the projects/files from the one database to the other. On the other hand I can also use a full backup tape to restore the software and database on the new server. Has anybody had any experience with this or any suggestions about either approach. Thanks for any input. Chris
-
Early in the coming New Year, I will be setting up a new development sever that will replace an very old and tired one. One of the software components that must be moved is the MS Visual SourceSafe software and database. I know that I can install the VSS software on the new server, but I can not locate any type of utility that will 'move' the projects/files from the one database to the other. On the other hand I can also use a full backup tape to restore the software and database on the new server. Has anybody had any experience with this or any suggestions about either approach. Thanks for any input. Chris
Just copy the sourcesafe directory on the server to your new server over the network. There is nothing "installed" on the server, it's just a bunch of files in a directory (unless the server is also being used as a client, in which case you can just run the netsetup out of the directory to insall the needed files). Then you need to change the clients to point to the new machine, unless you plan on giving the new machine the same name as the old.
-
Just copy the sourcesafe directory on the server to your new server over the network. There is nothing "installed" on the server, it's just a bunch of files in a directory (unless the server is also being used as a client, in which case you can just run the netsetup out of the directory to insall the needed files). Then you need to change the clients to point to the new machine, unless you plan on giving the new machine the same name as the old.
Thanks for the input Erik. Sounds like it should go pretty straight forward. I was just concerned cause the docs talk about running a few programs to create a new database. But if the programs are just creating the directories and file structure that VSS wants to use, the recursive file copy should do the trick. Thanks again. Chris