Why SSISDeploy overwrite the whole projects and not only what was modified?

Question

I have the below structure in ssis server:

Assuming I worked on Integration service project in VS but only on one dtsx from the list above. Now I ran the below SSISDeploy (documentation is here) command from CMD:

SSISDeploy.exe -s:"C:\git\test\Integration Services\bin\Development\Integration Services.ispac" -d:catalog;/SSISDB/TEST/TEST_INRG;"TEST03,1234" -at:win  

and got this message:

Will deploy 'Integration Services.ispac' to TEST03,2890:/SSISDB/TEST/TEST_INTG.   
The project 'TEST_INTG' already exists in the catalog folder 'TEST'. Will overwrite it.  

So what actually happened, all the packages were deleted from from the TEST project and my dtsx package was overwritten by the modified one. Is there a way to avoid it so the 'Integration Services.ispac' will change only what was modified? I was expecting to see only the change in the dtsx package which I worked on locally.

Answer 1

Hi @arielman2304 ,

A DTSX file corresponds with a single SSIS package.

The ispac contains all of the packages, plus some other project-level information, zipped up into an archive.

The ispac can be deployed to a SQL instance in one operation (all of the package and parameter information is transferred in one hit.)

So when you use the SSISDeploy cmd to deploy the 'Integration Services.ispac' , it overwrites the whole project.

Single package deployment in SSIS you may refer: https://www.sqlshack.com/single-package-deployment-in-sql-server-integration-services-2016/

Regards，

Zoe

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October

Answer 2

I got official answer from Microsoft:

ssisdeploy.exe will override the whole project, which means it'll not only override the changed packages, but also the unchanged packages. For now, there's no such way to only deploy the changed packages.

Which is strange, as they have other tool which can do it (Deploy Single SSIS Package):
https://www.tech-recipes.com/rx/77912/how-to-deploy-ispac-file-ssis-package-from-command-line/