Tim Elhajj

One IT PRO writer vs. all of MSDN

How to Install SQL Server 2008 for TFS 2010

15 Comments

This video goes through SQL Server installation for Team Foundation Server 2010. I did the SQL Server install as if it were for the TFS 2010 standard install option (the one with TFS and all the SQL Server features on one server), but I’ve included enough information in the audio track that it ought to be helpful whatever SQL Server topology you want to create. I am using SQL Server 2008 R2, but it’s almost exactly the same installation as the original SQL Server 2008.

If you want text to follow along with the video or to review afterwards, this MSDN topic on installing SQL Server 2008 for TFS 2010 will get you really close. I never updated the topic for the SQL Server R2 release. I remember discussing it with the team when R2 released, but we felt it was close enough that people would manage. If people are interested in an update, it’s still an option.

I’ve been teaching myself how to do instructional screen capture videos and this is my first effort. I’m pleased with how it came out. If you like it, let me know. If you have feedback on this video or suggestions for future videos, I’d love to hear it in the comments. I think video might be helpful, especially for server installation tasks.

Author: Tim Elhajj

Tim is probably walking his dog.

15 thoughts on “How to Install SQL Server 2008 for TFS 2010

  1. Pingback: March 17, 2011 – VS/TFS Links and Quick Hits | Learn TFS

  2. Pingback: How to Install and Configure MOSS 2010 for TFS 2010 « Tim Elhajj

  3. One thing I think you may have missed (please correct me if I’m wrong) is that SSRS (Reporting Services) is not really set up until you run the “Reporting Services Configuration Manager” at least one time where it performs a variety of crucial initialization tasks (where the user has the ability to tweak some settings before each initialization task). One area that is *most* important in setting up SSRS is to make sure that the “Report Server Mode” *must* be set to ‘Native’ (not ‘Sharepoint Integrated’). It should also be noted that the SSRS Config Manager must be run as Administrator.

    I would say that my experience has been that the preparation of a SQL Server 2008 R2 database instance for use as the data tier of TFS 2010 is not complete until the SSRS Config Manager has been run and each tab (on the left-hand side of the wizard) has been selected and initialized. I have had to tear down and reinstall TFS 2010 numerous times due to the SSRS integration not working properly as a result of my not realizing that the SSRS Config Manager had to be run and traversed before the TFS install.

    One of the things I’ve noticed about these newer Microsoft server installers is the separation of the installation from the configuration. Overall, it an excellent progression but, historically, installation included the preliminary, initial configuration of the software package; with this new style, I am finding that the configuration tool must be run to truly complete the initialization of the software system. The server systems that follow this pattern include TFS 2010 and MOSS 2010 but their installers always try to get you to kick off the configuration tool as their closing step in a daisy-chaining effect. I feel that SSRS’s configuration is not sufficiently linked to its installer and, thus, it leaves us hanging where we don’t realize that SSRS is not really ready for action.

    Thanks for you excellent work.

  4. Robert, thanks for the kind words about the work. You have an excellent point about not using “SharePoint Integrated” in SQL Server, if you install Reporting Services. As you point out, you have to use Native mode to get it all to work.

    SQL Server will setup Report Services for you during SQL Server setup, if (*and only if*) there is an instance of the Database Engine on board the server. If not, the option for SQL Server to set it up will be greyed out, and you’ll have to set it up manually, post install, as you point out. Here is a link to the docs on how to do it: http://msdn.microsoft.com/en-us/library/dd578652.aspx#ManualConfigure

    Another thing you have to watch with Report Server, especially if it’s installed on a server other than the server where you’re running TFS, is that you have to permission the Report Server so that the person installing TFS has local Admin rights, and you have to add the account you’re using for TFSService into the Report Server tool so that TFSService is in the Content Manager role. Here is a link to the docs on how to do this: http://msdn.microsoft.com/en-us/library/dd631908.aspx

    I’ve been thinking about doing a video on how to setup the Report Server if it’s not on the same server as TFS. There are the extra steps you have to take to run Reporting Services Configuration Manager (completely agree that SQL should launch a wizard al’a TFS/SharePoint to get this done post install — Come on, SQL Server install team, it’s 2011 already!) and the permission issues to contend with that make it just tricky enough. An even bigger can of worms is getting an existing project to work with a newly added (or moved) report server. That’s actually a complicated enough process it would need its own video, separate from the how to install and configure the report server on its own server video!

  5. Pingback: Installing the Standard Configuration of TFS vNext from the BUILD Conference in Los Angeles « Tim Elhajj

  6. Pingback: Installing the Standard Configuration of TFS vNext from the BUILD Conference in Los Angeles - MSDN Blogs

  7. Pingback: Installing the Advanced Configuration of TFS vNext from the BUILD Conference in Anaheim « Tim Elhajj

  8. Pingback: Installing the Advanced Configuration of TFS 11 from the BUILD Conference in Anaheim « Tim Elhajj

  9. Catch 22 on the ‘native’ vs ‘sharepoint integrated’ reporting….if you choose native you do not get the rich reporting available….through use of SharePoint dashboards, execel services, etc….at least this has been my experience. There is some major ‘tweaking/config’ needed in setup of ‘sp integrated’ and you lose the ‘ease of use’ of native with pure TFS reporting….bummer

  10. Hello Anon!

    In Dev10, we enabled SharePoint dashboards in TFS. If you are using SharePoint Foundation or SharePoint 3.0, you don’t need to do any special configuration. If you’re using MOSS, you do have to make some SharePoint configurations, but you should never have to use “SharePoint Integrated” in SQL Server install. In fact, doing so will break TFS, and requrie “major tweaking/config” as you wisely point out. I haven’t actually done any of the tweaks myself. If you want some guidance for getting MOSS (2007 or 2010) configured for TFS, look here on MSDN: http://msdn.microsoft.com/en-us/library/ff803408.aspx

    I’ve also got some video on this site that helps you manually configure MOSS 2010 (same as the 2010 instructions on the page above). Look here for the video: http://elhajj.wordpress.com/2011/07/01/manually-configure-moss-2010-for-tfs-2010/

    Good luck. Let me know how you make out!

  11. We have installed TFS 2010 and RS native mode on one server, dbs on a second, existing SQL 2008 R2 server. We have integrated TFS with an existing, customer-facing, Kerberos SharePoint 2010 that was already integrated with a previous instance of RS. We are getting a name conflict in SP when we try to create a new Team Project:

    2012-07-24T09:38:56 | Module: WSS | Thread: 18 | Activating SharePoint Feature: 0d953ee4-b77d-485b-a43c-f5fbb9367207
    —begin Exception entry—
    Time: 2012-07-24T09:38:58
    Module: WSS
    Exception Message: Server was unable to process request. —> “Reports” cannot be used as a site name. Site names cannot contain certain reserved words and cannot begin with an underscore. Please enter a different name. (type SoapException)
    Exception Stack Trace: at Microsoft.TeamFoundation.Client.SharePoint.SharePointTeamFoundationIntegrationService.HandleException(Exception e)
    at Microsoft.TeamFoundation.Client.SharePoint.SharePointTeamFoundationIntegrationService.ActivateFeatureById(String webApplicationUrl, String absolutePath, Guid featureId)
    at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.HandleFeatureActivation(WssCreationContextWrapper contextWrapper, XmlNode features)

    — end Exception entry —

    Any ideas on how to resolve this mess? Thanks.

  12. Randall, I haven’t seen this issue before. Does your TFS installation use “Reports” as a site name? What happens if you change the name? Is there a TF error number associated with the error? This might be a good question to ask at Serverfault. If you give me some more details, I can poke around a bit more.

    Tim Elhajj

  13. Tim, thanks for responding so quickly!

    No, we haven’t explicitly named a SharePoint site or a TFS team project collection or team project, or a Reporting Services folder as “Reports”. There was no TF error number that I say, perhaps because it seems to be reported by SharePoint.

    We are currently ripping out our team project collection and SP site collection, as we made the TFS service account/reports account an SPN after the collections were created, hoping that now with Kerberos seemingly in place, we will get better results.

    Any other ideas you have would be appreciated.

    Thanks again!

  14. Pingback: On Dealing with TFS error TF400533 « Tim Elhajj

  15. Pingback: Installing the Advanced Configuration of TFS 11 from the BUILD Conference in Anaheim - Visual Studio ALM + Team Foundation Server Blog - Site Home - MSDN Blogs

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 924 other followers