Killer is rebuilding our internal file server, a Windows Server 2000 box that’s begun creaking. It also hosts our source control. So after 6 years of saying “we wish”, we’re finally going to take the plunge and try another source control solution.
Of the several we considered/evaluated, right now it seems to be a choice between Surround SCM and Visual Studio Team System 2008. Since licensing Team System also gets us an IDE/Compiler/Profiler/Analyzer, and since our attempt to import our VSS database to our Surround License went arse-over-tit, we’re going to try VSTS.
I missed the prerequisite that you have Microsoft SQL Server 2005 SP1 or higher installed when I downloaded the VSTS 90 day trial. When the VSTS installer wanted the address of an MSQL server, I pointed it at the “Developer Express” edition Visual Studio 2008 had installed. Not good enough. Ok. Break out the MSDN disks and install from there.
Not for the feint of heart – MSQL install asks some seriously tough questions (for someone who’s gotten out of the habbit of administering Microsoft apps).
Once you’re done, it presents you with a nice little window showing you the items to be installed and the order of installation… And then proceeds to install them in a seemingly random order, only to uninstall and reinstall some of them after installing dependencies. I swear it backed up, uninstalled and reinstalled MSXML6 no less than 11 times.
In total, it took it over 3 hours to install MSQL from 2 CDs, and I’m not entirely sure I gave it the right answers.
I guess I will be finishing this install via Remote Desktop over my VPN…