June 5, 2014 at 5:56 am
Hi there
I am trying to deploy a package to a project in my SSIS catalog and am using the following command:
dtutil /FILE C:\Changes\ReceivedEDI.dtsx /DestS MARSQL12 /COPY DTS;TradingPartners\TradingPartner\ReceivedEDI
Where the TradingPartners is the folder name, the TradingPartner is the project name and the ReceivedEDI is the package name.
I am getting an error of:
Error (0x800706BA) while checking for the existence of package "TradingPartners\
TradingPartner\ReceivedEDI" in the SSIS package store.
Error (0x800706BA) saving package "TradingPartners\TradingPartner\ReceivedEDI" t
o the SSIS package store.
Can anyone explain what I am doing wrong?
Thanks
June 5, 2014 at 6:01 am
Dtutil can only be used for deploying packages in the package deployment model.
It cannot be used for the project deployment model (which uses the SSIS catalog).
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 5, 2014 at 10:59 am
Oh, so whats the best way to deploy a package to an existing project in SSISDB?
June 5, 2014 at 11:03 am
Kwisatz78 (6/5/2014)
Oh, so whats the best way to deploy a package to an existing project in SSISDB?
There are a few options:
SSIS Deployments with SQL Server 2012[/url]
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 5, 2014 at 11:27 am
OK your article says:
In SSIS 2012, the unit of deployment is a project. This lets you deploy everything at once: all the packages, parameters and connection managers. This has, of course, impact on how you need to structure your deployments: when you alter a package to fix a bug, you cannot deploy this single package. You need to deploy the entire project.
Bit of a limitation in deploying a new\fixed package to an existing project 🙁
June 5, 2014 at 1:16 pm
Kwisatz78 (6/5/2014)
OK your article says:In SSIS 2012, the unit of deployment is a project. This lets you deploy everything at once: all the packages, parameters and connection managers. This has, of course, impact on how you need to structure your deployments: when you alter a package to fix a bug, you cannot deploy this single package. You need to deploy the entire project.
Bit of a limitation in deploying a new\fixed package to an existing project 🙁
True unfortunately.
Time to get everything in source control and start branching and merging.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply