Post reply

SSIS Source Control

  • February 25, 2020 at 2:53 pm

    #3728603

    We use Git on Azure DevOps – and that is what I would recommend. In my opinion, it's way faster and more lightweight to use than TFS.

    When you say that Git is the 'wrong fit' for you, can you be a bit more specific?

    Also, as you are all going to be working on a single project, you are in for a hard time, regardless of which VCS you use. That's because SSIS projects and packages don't merge very well, if at all.

    That's for a couple of overall reasons:

    1. You have a shared project file, which is updated whenever packages are added or deleted, or when project-scoped parameters or connections are added, amended or deleted. Merging these can be tricky, but it's possible, if you know what you're doing.
    2. If two developers modify the same packages, merging the changes into a single package containing both sets of changes is unlikely to work – the structure of SSIS packages is too complex, despite them being XML. You need to ensure that the devs work on separate packages to avoid this (which should be easy enough, as there are not many of you).

    If you are able to split the packages into multiple projects, by grouping them somehow, it will make things easier for you.

  • February 25, 2020 at 3:21 pm

    #3728616

    We personally use Subversion at the office. It's fine for other Visual Studio Projects, and VSCode, however, it isn't great with SSRS and it's literally awful with SSIS. Unfortunately I'm stuck with suffering with what we have, so this is just my input of don't use Subversion with SSIS.

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

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

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