Hello,
the new environment I am working at now wants to use GitHub for version control, and SSIS for ETL, and wondering if SSIS integration catalog will work well with GitHub? or is it only going to work with SSIS by file?
thanks in advance
Hello,
the new environment I am working at now wants to use GitHub for version control, and SSIS for ETL, and wondering if SSIS integration catalog will work well with GitHub? or is it only going to work with SSIS by file?
thanks in advance
No, it does not work how you describe.
SSIS development should work with SSIS projects and solutions in Visual Studio, and it is these which should be pushed to GitHub.
It is then up to you to create suitable DevOps processes to deploy the packages from the relevant GitHub branches (QA/Prod etc) to your SSISDB instances.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
March 3, 2020 at 5:01 pm
thanks again for your assistance Phil, so what I am getting at is (I am slow sorry), is it does work with Integration catalog SSISDB, BUT you have to push/pull the entire project/solution and cant do just the individual package itself correct?
March 3, 2020 at 5:06 pm
Since SQL Server 2016, single package deployment to SSISDB has been possible.
What you choose to push to GitHub is entirely under your control, on a file-by-file basis, as long as you know what you are doing.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
March 4, 2020 at 9:46 am
thanks again for your assistance Phil, so what I am getting at is (I am slow sorry), is it does work with Integration catalog SSISDB, BUT you have to push/pull the entire project/solution and cant do just the individual package itself correct?
Integration Services Catalog and Source Control aren't related; at all. How you choose to deploy your packages/projects and how you choose to your source control are 2 completely different choices.
With the SSIS Catalog you can deploy both packages and Projects, however, the former is only available in SQL Server 2016+; as Phil points out. With Project Deployment, you don't have to push the whole Solution, no. So you can have multiple projects in a Solution and just deploy one of them. Personally, if you do have multiple projects, I would suggest deploying them separately anyway.
As for your Source Control, that's completely up to you. If I recall, Phil uses Git for his Source Control, so he'll be able to give better insight that I on it. I personally use Subversions (and I hate it), so I don't know how well Git integrates with SSIS.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
March 4, 2020 at 12:18 pm
... so I don't know how well Git integrates with SSIS.
Git's just another VCS – it monitors and tracks changes to files. There's nothing in Git which is specific to SSIS.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply