Source Control

  • Hello,

    We are in the process of migrating from SQL 2008 to 2012 (can't go to 2014 since two of our vendors are not certified). We also received new computers last week so we made the decision to install just the 2012 SSMS. Works great!

    We are also migrating our development environment from Visual Studio 2010 to 2013. So we only installed 2013. Again, works as expected and talks to our TFS 2010 server perfectly.

    Our Team Foundation Server is still running version 2010. We have 2013 in hand and are ready to migrate but can't until SQL 2012 is up and running on the server.

    With the background now stated, here is my question. On our old computers, we had our SSMS 2008 talking to TFS 2010 for source control purposes by downloading and installing the TFS MSSCCI provider. VS 2010, SSMS and TFS were all happy together. The dilemma we have now is getting SSMS 2012 to talk to our TFS server. The MSSCCI provider looks like it has to match the server version so I downloaded the 2010 provider but it won't install saying that VS 2010 isn't there, which is correct. We don't want to install VS 2010.

    How can I get SSMS 2012 to talk back to our TFS 2010 server? Or, am I just stuck until we get TFS upgraded and then download the MSSCCI provider for 2013?

  • Never seen that working, so kudos for making it work. Most people move to SSDT and DB projects or they can use Red Gate's SQL Source Control to integrate.

    Disclosure: I work for Red Gate.

  • I don't work for Red Gate (although I am a Friend) and I can recommend their Source Control product too.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply