SSIS Parent package Deployment model

Hi,
I'm converting a SSIS 2008 R2 solution with multiple project to SSIS 2014, one of the projects stores only parent packages and these packages are calling packages in other projects. Using project deployment with project reference I guess this is not possible.
But can I have a parent package in package deployment model project and then call child-packages in project deployment model? Can I set values in an SQL Server Agent Job that sets project parameters?

Hi perwi,
I think in this scenario just convert, the legacy mode should be used and make sure the conversion is successful, only then try switching to Project Deployment.
Nothing can be set in the Agent, but in the Catalog (SSISDB).
Arthur My Blog

Similar Messages

How can I use UC4 instead of SSIS Master Package deployed using project deployment model?

Hi Folks,
My team is planning to opt UC4 for scheduling the SQL Jobs and I have to come up with a plan to integrate it.
As of now, I do not have software licence in place to do some research.
If you have worked on it, can you tell me that how can I schedule SSIS packages using UC4.
Also, we are using SSIS project parameters (Project deployment Model). What kind of changes I have to make in SSIS packages to support UC4. Is it possible to pass parameters to SSIS package through UC4? If not, is there any alternativ?
Appreciate your help!
Gaurav Gupta

If you have access to Automic Community, there are details there on how to execute SSIS 2012 packages deployed in SSISDB catalog (project deployment model). Here is the link:
https://community.automic.com/discussion/4878/how-to-execute-sql-server-data-tools-ssdt-2012-package-synchronously-using-sql-job
Leonard

Use Package Parameters in Package Deployment Model

Can you use Package Parameters when you use the Package
Deployment Model? The Parameter tab is visible in SSDT and in SSDT they seem to work, but can you use them outside SSDT? In a SQL Agent Job or on the command prompt?
And if not... why is the tab visible? ;-)

Hi HansAnderss,
Integration Services (SSIS) parameters allow us to assign values to properties within packages at the time of package execution. We can create project parameters at the project level and package parameters at the package level. But the use of parameters
are only supported in Project Deployment Model, we cannot use parameters in Package Deployment Model. This is by design.
Just as you said, we can also see the Parameters tab in Package Deployment Model. And I couldn’t find a way to hide the pane. If you have concern about this issue, I recommend you that submit the requirement at
https://connect.microsoft.com/SQLServer/. If the requirement mentioned by customers for many times, the product team may consider to add this feature in the next SQL Server version. Your feedback
is valuable for us to improve our products and increase the level of service provided.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SQL 2012 SSIS Single Package Deployment

I have the following scenario:
I have a 2012 SSIS project that contains two packages and on the release of the project, I deploy the entire project solution which has both packages. I then create a SQL Agent job that executes the packages from the SSIS catalog and all is well.
Down the road, a change is required for both packages and both packages are being developed. The first package change is ready to be deployed and the business wants the change to be implemented and does not want to wait for the second package development.
How do I deploy my project to get the first package deployed without overwriting the second package? I do not want to drop out the second package from the project because the agent job is depending on the package to be located in the catalog. However, I
cannot just create a new project deployment with the second package changes since the second package is not ready to be deployed yet.
Is this possible? In the deployment wizard, nothing is available to select only a specific package to update.
I want to take advantage of the SSIS catalog for configuring connections, parameters and the like but this ability to replace a single package needs to be available.
Can we do something in Powershell to add the updated package to the packages collection, which will overwrite the existing package or would that mess up the project deployment and the OOTB versioning that exists?
Or, is the workaround to create a new project with the Package One Updates and the original Package Two, walk through the deployment wizard to create the ISPAC file and then deploy that project to the catalog. (I guess answering my own question here but
really hoping for something more elegant)
Thanks in advance
Chuck

I agree completely with Mahesh.
Ever since the days of UNIX makefiles, only those parts of a project which have changed have been recompiled.
Indeed for instance, Visual Studio does this by default when building .NET projects, C++ etc - only what has changed is rebuilt, I mean it makes sense. Why waste time rebuilding something that hasn't changed at all.
I do not understand why an SSIS project requires the full redeployment of every single package when only one may have changed - it seems incredibly risky and exposes us to inadvertently deploying changes in other packages that we don't want to.
The workarounds described above that involve branching/merging etc in order to only be able to deploy a portion of a SSIS project may work to reduce that risk - but they can hardly be called 'best practice'. We risk end up making a mess of our version histories.
It would be good to get some direction from Microsoft on why it has been implemented the way it has, perhaps there is something we don't understand - in particular the decision to compile all packages into a single .ispac - after all, that's the source of
our problem here.
It would be handy to have a smaller target unit of compilation - again, forgive my possible lack of understanding here, but what is the reason for the granularity of deployment to be at the project level, and why wasn't the target of deployment simply kept
at the package level?
That was the massive change from 2008R2..
Thanks! Josh

How to run ssis 2012 package deployed on SSISDB using stored procedures from [SSISDB].[catalog] by regular AD accounts ?

Hello, I need to run ssis package by stored proc(pass parameters inside and get result using stored procedures [SSISDB].[catalog].[create_execution]) etc. Do not suggest me to use SQL Agent here as this is not the case. or by pass this using configuration
for SSIS, I need to know what permission I'm missing if those stored proc run by AD account, with rights described from BOL and I'm having "The current security
context cannot be reverted. Please switch to the original database where 'Execute As' was called and try it again." If I schedule stored proc to run by Agent and specify parameters - will work, from remote PC - does not. I have sysdamin
rights on the server where SSIS and stored proc which is call it exists. I was digging around and have ugly solution to make it working, I want to use elegant solution using those stored proc from [SSISDB].[catalog] ...
Any help especially from Microsoft guys here...?
Vladimir

>>>>If I schedule stored proc to run by Agent and specify parameters - will work,
from remote PC - does not.
Vova
If you schedule the job it will be running under SQL Server Agent account security.... What error
do you get when you run the SP from remote PC?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Package Configuration Wizard or Project Deployment Model

I am using SQL Server 2012 and I have multiple SSIS packages working in DEV.
My aim is to deploy these to File System for execution by a Windows Service application. Should I therefore using the Package Configuration Wizard for storing DEV and PROD server details?
Is the Project Deployment Model only required when deploying to SQL Server?

Hi DarrenOD,
The project deployment model enables you to deploy your projects to the Integration Services server. And there are some features like Parameters, Environment, Environment variables, SSISDB catalog and Catalog stored procedures and views that are available
to projects developed only for the project deployment model.
After converting project deployment model to package deployment model, there are four steps in the package deployment process:
The first optional step is optional and involves creating package configurations that update properties of package elements at run time. The configurations are automatically included when you deploy the packages.
The second step is to build the Integration Services project to create a package deployment utility. The deployment utility for the project contains the packages that you want to deploy.
The third step is to copy the deployment folder that was created when you built the Integration Services project to the target computer.
The fourth step is to run, on the target computer, the Package Installation Wizard to install the packages to the file system.
Reference:
Deployment of Projects and Packages
How to: Deploy a Package
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

How to deploy and execute SSIS 2012 packages when only SSDT is installed

Hi, I am facing a weird situation where we did an upgrade for visual studio to vs 2102 on all the dev machines and as part of that moved to SSDT from BIDS but all the database is still SQL Server 2008 R2. Now I have a few SSIS 2012 packages which I cannot
schedule & run because DTEXEC.exe is not compatible and I get all sorts of version & “Package Load error 0xC0010014 in CPackage::LoadFromXML” error even though I set it up in 32-bit mode and was trying to save it to msdb. I knew I will not be
able to schedule this as a job in SQL Server Agent but even saving the package does not work.
Thanks in advance............
Ione

I doubt 2012 ssis packages are backwards compatible with 2008r2. 2008r2 doesn't know anything about the project deployment model and i'm sure there's new tasks and connectors in 2012 so the package deployment model ssis packages won't work either.
You will need a sql 2012 integration services service installed and running somewhere. You need this to execute your 2012 packages
Jakub @ Adelaide, Australia Blog

I have deployed SSIS Package to Integration Services Server, Can i still call them in Parent Package

i have deployed SSIS Package to Integration Services Server, Can i still call them in Parent Package

Hello,
In SSIS 2008 you have to adjust your parent package in Visual Studio and point to the deployed package, as ArthurZ stated.
In SSIS 2012 with projects in project deployment mode this has become easier: you can call the child package in your project from the main package and it will use the package in the development. then you can deploy the project ot SSISDB and the
Main package in there will call the child packages in the SSISDB.
Jan D'Hondt - SQL server BI development

Individual SSIS Package deployment in SQL server 2012

Hi,
I am developing the SSIS packages in sql server 2012.
I want to know how we can deploy individual SSIS packages as I will be editing the required packages if need be then I have to deploy that package only instead of entire project deployment.
Please help me on this.
Regards,
Ramu
Ramu Gade

Hi Ramu,
According to your description, you want to deploy a single package instead of entire project in SQL Server 2012.
In SQL Server 2012, the unit of deployment to the SSIS catalog is a SSIS Project. Each SSIS project contains one or more SSIS packages. We couldn’t directly deploy a single package in Project Deployment Model.
To work around this issue, we can refer to the following suggestions:
SSMS-->Integration Service Catalogs-->SSISDB-->Your project-->projects. Right click on the projects, and choose "Import Packages...". Then make use of the Project Conversion Wizard to select the packages that you want to deploy, deploy
the generated .ispac file to SSIS Catalog.
The command line tool DTUTIL.EXE which can be used to deploy SSIS packages.
References:
SQL Server 2012 - Project Deployment Model - Deploy a single package
Command line deployment tool for SSIS packages
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS 2012 Project Deployment with included EXE application not deployed in Catalog

Hi,
I have converted a SSIS solution consisting of 20 packages, two exe applications, and a web service to the project deployment model. My question is: where are the exe applications deployed to? I don't see them in the catalog on the server. If I exclude
these from the solution and disable the steps in the packages using them, everything works fine. In BIDS, I can include the exe applications and run the solution locally and it works fine. I have parameters for the path to the EXEs, but when configuring
the path in the catalog, I am unsure what to set it to. Do I need to manually move these EXE applications to the database server separately from the deployment?
THanks much,
Pat

You can even put exes as files in file system in a shared folder and access them from packages in catalog. Just pass the paths (UNC) using parameters in package
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Script Editor takes forever to load with SSIS 2012 packages in VS 2012 when you click on Edit Script... button

Hi,
I'm upgrading some SSIS Packages to the SQL 2012 Project deployment model. However, when I click on the Edit Script... button in a Script Editor Task, Visual Studio just sits there for minutes until it sometimes opens, sometimes doesn't. Surely this should
open up pretty much instantaneously. Can anyone shed any light on why this is happening ?
Thanks
Dave Evans

Hi Dave Evans,
It might be due to permission issue, please try to uncheck "Check for publisher’s certificate revocation" under the "Security" group in "Advanced" tab in "Internet Options", please see:
http://stackoverflow.com/questions/13540151/ssis-script-editor-loads-very-slow
Thanks,
Eileen
Eileen Zhao
TechNet Community Support

Failed to locate project named ... in SSIS 2012 package scheduled in agent

Hi
I have 2 packages that are deployed using Project deployment model on a, the are scheduled to run every 1/2 hour, for the last 2days the have been failing with Failed to locate project named ...:A .Net framework error occurred during execution of user defined
routine or aggregate "decript_binarydata": System.IO.LoadException Could not load file or assembly.....The thing is that the package was working without issue, this seems to be a decryption issue, so I believe it is to do with Project Deployment
model, but I am not sure
Any help would be much appreciated
Regards
Andy
CRM 4, SQL Server and .Net developer using C#

Hi Andy,
Based on my research, please refer to the following suggestions to fix this issue:
Change the SQL Server Service Account from built in default “NT Service\MSSQLSERVER“ to another account with admin rights on the system.
Grant appropriate permissions to SQL Server Service Account & SQL Agent Service Account.
1. Note down your SQL Server Service Account & SQL Agent Service Account.
2. Go to Start-> Run-> secpol.msc-> Local Policies->User Rights Assignment
3. Check if these 2 accounts are a part of the following policies.
    • Log on as a service
    • Act as part of OS
    • Adjust memory quotas
    • Logon as batch job
    • Replace a process level token
4. If not, add them explicitly.
5. Reboot the machine
Repair the SQL Server instance to test the issue again.
The following two blogs are for your references:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2012/08/20/error-while-deploying-ssis-2012-project-from-ssdt-to-ssis-catalog-system-componentmodel-win32exception-a-required-privilege-is-not-held-by-the-client.aspx
http://blog.oraylis.de/2013/09/fixing-sql-2012-ssis-deployment-error-6522-a-required-privilege-is-not-held-by-the-client/
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

SSIS 2012 package runs under SSDT but fails with permission error from SSMS

I have a simple package that pulls data from a text file located on a Windows file server that runs successfully from SSDT on my client.
However, when deployed and running the package via SSMS from the client, the package fails with a permission error, with the error stating that the data file could not be opened.
I have done some investigation and have seen some info that states that a package run from SSMS runs under the account on which you are logged on to the machine, which I would have thought is correct. This is therefore the same account when running from
SSDT (which works) and I can see from the SSIS Report that the 'Caller' is stated as my account, so if this is the case why isin't the package working.
I've also seen an MSDN forum answer which stated the opposite that the package when run from the IS Catalog in SSMS doesn't run under the account on which the client is logged on with, which is the opposite of the above, but doesn't indicate which account
it is using.
So what account is being used to run SSIS 2012 packages from the IS catalog from within SSMS ?
If it is the account on which you are logged onto the client running SSMS, why is it not working when the account has the necessary permissions (as provent when running from SSDT) ?

I am aware it's using my account and not one of the service. There's nothing in the posts above which suggests I'm using the service account. I don't know why people keep assuming that I'm running the package from a job. I've never stated that in any of
the posts I'm running the package from a job. It's been made quite clear I'm running the package from the IS Catalog on SSMS:
"This is simply selecting a package from the IS Catalog, right-clicking and selecting Execute package.", as per the Nov 18 post, and in the original post "....So what account is being used to run SSIS 2012 packages from the IS catalog from
within SSMS".
Just to be clear, the package is NOT being run from a job. It's using the Execute package option when selecting the package within SSMS from the IS Catalog and it's running under the account on which I am logged on to my client.
Please read carefully. I was just answering your question "So what account is being used to run SSIS 2012 packages from the IS catalog from within SSMS ?" and stating that you where right and that it uses your account to run the package
when you execute a package manually from the Catalog and that you can prove that by logging the system variable.
A good suggestion about using a share in the task to map the drive and I will try this. I would find it strange that SSMS requires this mapping whereas SSDT does not though.
Ok let us know your findings. If it doesn't work you can also test it with a password and username:
net use f: \\financial\public yourpassword /user:username
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter

Error running child packages from parent package - Error 0xC0011008

Hey...
I am running a parent SSIS package (running sp2, 9.0.3042) that calls several child packages.
On our development server, we now cannot run this because we get 1 or more of these errors:
"Error 0x80004003 while preparing to load the package. Invalid pointer . "
"Error 0xC0011008 while preparing to load the package. Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored. . "
It is not occuring on the same packages. It varies every time it is run.
I can run every one of the child packages individually, using the same login ID that the parent is executed under.
The parent package works fine on my local machine and other servers running the same version of SSIS. Just not on this server.
Does anyone have any ideas???
Thanks
BobP

I have the same error with no parent child package relationship. I have changed the "Max Concurrent Executables" in each package from -1 to 10 and got no change. My code is below:
List
<string> fileList = new List<string>();
private
void checkedListBox1_SelectedIndexChanged(object sender, EventArgs e)
//this.fileList.Add(checkedListBox1.SelectedValue.ToString().Trim());
this.fileList.Add("name");
private
void button1_Click(object sender, EventArgs e)
string @fileName;
foreach (string str in fileList)
@fileName = str;
string pkgLocation;
Microsoft.SqlServer.Dts.Runtime.
Application app;
DTSExecResult pkgResults_Sql;
pkgLocation =
@"C:\" + @fileName + ".dtsx";
app =
new Microsoft.SqlServer.Dts.Runtime.Application();
Package pkgIn = new Package();
pkgIn = app.LoadPackage(pkgLocation,
null);
pkgResults_Sql = pkgIn.Execute();

Weird question in SSIS 2012 package

hi folks:
I've created a SSIS 2012 package in my local machine using
Microsoft SQL Server Integration Services Designer
Version 11.0.3436.0
This package contains a script task using .NET framework 4 .
Everything works fine and I decided to deploy to the QA server.
On the QA server, the package wont' work then I decided to open in the SSIS designer with the same version 11.0.3436.0
This is when this weird things happens.
On the QA machine, when I opened this deployed pkg directly in SSIS designer and ran it, the pkg failed with the error pointing to the script task.
Then, I literally opened the script task and closed it WITHOUT changing anything .
After that, I ran the same package in SSIS designer... Guess what, it worked!!!
Weird! could anyone here help explain what just happened? this makes my deployment process a nightmare as I have to literally opened the script task after it gets deployed and change the pkg location as SSIS designer will save the "good"
pkg in a different location other than deployed one.
Thanks a lot!
hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Hi cat_ca,
According to your description, the first time you run the SSIS package in SSIS designer, the package failed with the error pointing to the script task, you opened and closed the script task and re-run the package, it worked fine.
When we debug the SSIS package, the script component will be compiled to binary. In this case, the binary reverse failed due to some reason, so the script task is not normally build. To troubleshoot the problem, we can make use of logging feature to monitor
execution of an SSIS package.
For more information, please refer to the following documents:
https://msdn.microsoft.com/en-us/library/ms136033(v=sql.110).aspx
http://stackoverflow.com/questions/15004109/can-you-monitor-the-execution-of-an-ssis-package-in-bids-as-it-runs-on-the-ser
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.
Wendy Fu
TechNet Community Support

SSIS Parent package Deployment model

Similar Messages

Maybe you are looking for