Incremental Package Deployment – A SSIS 2016 Feature

Question

Incremental Package Deployment – A SSIS 2016 Feature

shubhankarthatte

Mr or Mrs. 500

Points: 589
More actions
August 28, 2017 at 10:38 pm

#325112

Comments posted to this topic are about the item Incremental Package Deployment – A SSIS 2016 Feature

Viewing 6 posts - 1 through 5 (of 5 total)

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

SMNayak Ten Centuries Points: 1214 More actions · Answer 1

thanks. But I wouldn't consider this incremental. May be "individual package deployment".
Incremental would be something where we (or the program) can identified the diff and deploy only the packages which are changed.

marc.de.vreese Newbie Points: 2 More actions · Answer 2

Hi, I have a problem with this package deployment method. When you set de "entrypoint package" off and you do a package deployment, the flag is not taken to the catalog. So we still need to use project deployment to get these flags to the catalog. Our processing depends on these flags. Is this resolved in future versions like 2019 ? (Those "entrypoint pakage" flags are kept in the project file of the solution)

Thomas Franz Hall of Fame Points: 3874 More actions · Answer 3

We can't use it either. We have an generic file loader, that searchs in the directories for new files and calls the fitting package to load the file. The (sub)package does the load job returns user variables (number of rows etc.) to the parent (the generic loader) who writes this into some logging tables. Saddly the return-a-variable-stuff does not work when we deploy just the single package...

God is real, unless declared integer.

mitchfields Newbie Points: 2 More actions · Answer 4

Does anyone know of a way to only deploy a single package between 2 SSIS Catalogs -- NOT using Visual Studio's package deployment feature. I want the version of the package from my QA/UAT environment (which I know has been tested) so I can deploy that to my PROD environment.

Thanks.

Phil Parkin SSC Guru Points: 246695 More actions · Answer 5

mitchfields wrote:

Does anyone know of a way to only deploy a single package between 2 SSIS Catalogs -- NOT using Visual Studio's package deployment feature. I want the version of the package from my QA/UAT environment (which I know has been tested) so I can deploy that to my PROD environment.
Thanks.

Deploying the package directly from source control would be the usual way of doing this.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.