Doctor Who 2 (1/3/2012)
Revenant, you brought up a couple of things. First, I think you made an excellent point that users would have to have to adhere to properly putting in header information into documents. Where I work, that isn't ever going to happen. So SP does that for you, then? I also notice that you mentioned that TFS is a specialized version of SP; that's interesting, as I've been thinking it would be good to migrate our very old instance of Visual SourceSafe to TFS. But the problem is identifying a server to put it on.
Lastly, does SharePoint require an administrator?
SP can reject a doc that does not adhere to a set template, or templates.
Re migration to TFS, TFS will run OK on a modest 4 GB machine, which may be virtual. TFS 2012 you will be able to run off the cloud.
Yes, TFS does require an administrator, and if you want to use it to manage the entire lifecycle, including but of course not limited to running automated tests on a dedicated test server - which can also be virtual - as is needed for repeatability, you will need a service account with admin rights to the Test Manager, the test server, and the TFS. I am mentioning it specifically because this powerful combination of privileges raises lots of security questions that better be answered before you start setting things up.
I think that TFS importance to SQLS development will increase because Visual Studio 2012 includes native tools for testing of SQL scripts including stored procedures. The argument that testing T-SQL under TFS is too laborious because you need custom wrappers will no longer hold water, so I would definitely recommend thinking about migration.