SQL Server on separate box?
I've been experimenting with TFS in a VM successfully, and now I want to roll it out for the whole team to use. The install process is a *lot* more painful than expected, and seems to have a bunch of rigid rules that make it difficult to fit into an existing server environment.
We wanted to use our existing corporate SQL Server install (just upgraded to 2005). SQL Server is on the "corporate" server, so I wanted to do the dual-server install to keep the minimal stuff on the corporate server and the application tier on a separate "Dev Team" server. One benefit (of many) is that I'm the Administrator on the Dev Team server, but not a domain Admin.
*But*, the corporate server is also the domain controller. And TFS Data Tier whines about being installed on a domain controller (for reasons that are not explained anywhere that I can find).
My question is: can I install TFS as a single server install (on the Dev Team server) but point it to the corporate SQL Server?
The only other option is to install a whole new SQL Server instance on the Dev Team server and TFS as s single server install. The downside is that we have a backup strategy that deals with the corprate server (including SQL Server), and it'll be a pain to have to come up with a new strategy to back up *two* SQL Servers.
*OR*, can I actually install TFS Database Tier on the domain controller (ie. what exactly is "not supported" in this case? What's the risk?).
I'm now falling *way* behind on my deployment plan because up till now I've had to involve IT in everything related to the corporate server.
First off, I am not a MSFT person and take everything I say with a grain of salt.
Up until Beta 3, TFS installation on a Domain Controller was not only ok, but it was encouraged in most of the VPC setup guides I saw. After that they put an install check to not allow this, mostly from a security standpoint of have a TFS service account having administrative rights on a domain controller (at least this was what I was told).
I personally do not see a problem with having the databases on it however. I don't know if there is something inherently in the application that would prevent this, but otherwise I can't see anything that would prevent you. As long as you can install the databases on the box (with or without the installer) you can run a utility to bind the application tier to a new database. I can tell you right now though, that Reporting Services and WSS might be harder to do this with than expected. I recently got done with a migration and rewrote a lot of the restore guide with my own knowledge of RS and WSS because the restore guide seemed to be wrong. WSS has a config and content database that have hardcoded links to the server and moving these can be tricky.
Hope this helps. Let me know if you need any additional information.
Many thanks. I was beginning to wonder if I was being ignored. :-)
After much consideration I decided to abandon the plan of "sharing" the corporate SQL Server and did a single-server install on what was originally to be just the application server. I'm decidedly displeased at having to "waste" processor cycles running a whole copy of SQL Server for no good reason, but on the other hand I'm decidedly worried about the overall stability of TFS; enough that I decided total isolation was the best practice.
It's all up and running now, and hopefully a future version will be a little more flexible in the setup options.
Brad.
Sorry, I only check the forums for unanswered posts every couple of days ;)
The install has actually improved dramatically since its Beta days, but it could definitely improve some on flexibility. I actually would like to pull Sharepoint off the TFS Server onto our company Sharepoint server, but thats not supported at all. Once you do get to the point where you want to pull the SQL Server to the other server let me know, I'll see what I can do to help you.
As far as stability goes, TFS itself has been pretty stable for me once everything is up and running. The only instability I've had with it is actually unrelated to TFS, it was our internal infrastructure.
