TFS and SSIS - Branching a package

  • I have branched a series of SSIS packages in TFS from a 2008 folder to a 2012 folder. The idea is to keep the history of the solutions / projects / packages and merge everything back into the main folder once our 2k8 migration to 2012 is complete. Due to a user request, I had to create a new 2008 package in one of our projects. So I created it, tested it, and moved it into Production.

    Now I have to upgrade the package to SQL 2012. I don't want to lose the history of the migration on the other packages in the project, nor do I want to reupgrade the rest of the project. I'd like to branch this new package to the upgrade folder and add it to the project without doing the Add Existing Package. Add Existing Package kills the TFS history. But just branching the package by itself only adds it to the project folder, not to the project file.

    Any thoughts on how I can branch the package from my 2k8 folder (with history) and get it added to the 2012 project (with history)?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Nevermind!

    Had to jump through some hoops, but here's what I did.

    1. Open upgraded project in Data Tools

    2. Add Existing SSIS Package from old project

    3. Go to Source Control Explorer window, right click package name, choose Undo Pending Changes. (This will keep the package name in the project's SSIS Package list but remove the package from the folder itself). EDIT -> If this doesn't work, start over and use Rollback

    4. In Source Control Explorer window, go to old project, right click the package, and Branch to the new project folder.

    5. In Source Control Explorer window, return to upgraded project folder, right click branched package and choose Check In. Enter comments and click Check In button.

    6. Resolve Conflicts window will open up. Choose Overwrite Local File and Folder. The conflict will clear.

    7. Pop back to Source Control Explorer Window and view the history of the package to see the previous history brought along with this package. (verification).

    8. Complete package upgrade and check it back in.

    YAY.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

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

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