SSIS package configurations

Hi Experts,
I am trying to configure my SSIS packages.
I have a master package to call child packages for Dimernsions and Facts.
Below are my two main approaches for configuration
1. Configuring all packages to read a single XML file for database connections and File paths.
In this case if someone want to change the location of config file then I need to change all my package. Is there any other issue with this approach?
2. Configuring via parent package variable. Here I will use the values from the parent package.
But after I did this , if we open the package the connection managers will throw error when we migrate to other server as the hard coding of the connection manager not matches with the actual database. If we run the master package it will
run successfully as it get the correct value from the master package.
Here Is there any way avoid this poping of error?
Please suggest what would be the best way ?
Regards
Mukejee

Hi Mukejee,
The error occurs because the variables passed from the parent child cannot get their runtime value in the child package at design-time. To avoid this issue, we can set the For your first approach, to avoid updating the Package Configurations after moving
to a new server, you can create environment variables on the each server, and export the relevant package configurations to the environment variables.
In reality, we can set the DelayValidation property of the Connection Manager as well as the Data Flow Tasks in the source package so that they don’t prompt for the error messages after being opened in the BIDS/SSDT on a new server.
Regards,
Mike Yin
TechNet Community Support

Similar Messages

SSIS Package configuration.

The SSIS packages is developed using BIDS 2008 and Database SQL Server 2008 R2.The package was developed in local box/Developement box and since the
connection string is pointing to local box , it works fine and data got loaded into the target tables.
When the SSIS packages is moved from Dev box to Pre Production or Production box , the package need to be modified since the database connection string
of local is different from Prod box.
To achieve the above process xml configuration has been done which contains the connection string details, but xml is pointing from the dev box path which might not exists in the prod box, so the package need to be open in Prod box and modify the xml file
path again, which the Client is not suppose to do..
To avoid that an Environment variable need to be created which will contain the xml path.
But xml is not that much secure compare to database configuration. So they advice us to configure by SQL Configuration.
The Configuration table will be created in the Db and with the help of SQL Job , the SSIS package will be scheduled, but if the tomrrow the database server
changes the package need to re open again and modify the connection string for the configuration tables.
Could you please suggest the best possible solution for SSIS package configuration when the User move the package from Dev box to Prod Box
with least possible modification.

Hi SubhadipRoy,
Just adding to ltz's suggestion. SSIS provides several options for handling package configuration values such as environment variables, XML files, registry settings, and a table in a SQL Server database. We can store the package configuration parameter values
in a SQL Server database table, then use those stored values when executing the package.
As per my understanding, I think this method is a better solution. Because when we move the package from Dev box to Production box, we can directly use simple T-SQL commands such as INSERT, UPDATE and DELETE to change the configuration data without changing
the package.
For more information about SQL Server Integration Services SSIS Package Configuration, please refer to the following blog:
http://www.mssqltips.com/sqlservertip/1405/sql-server-integration-services-ssis-package-configuration/
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS package give an error if execute through SQL server agent

I have created a SSIS package in BIDS 2012. If i execute this package through sql server agent it gives the below error:
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:19:47 AM Error: 2015-01-20
11:19:47.83 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.".
You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:47.94 Code: 0xC0016016 Source:
Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error
occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:48.04 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to
decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct
key is available. End Error Error: 2015-01-20 11:19:48.92 Code: 0xC00291EC Source: alter_keys Execute SQL Task Description: Failed to acquire connection "mstr_warehouse". Connection may not be
configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:19:47 AM Finished: 11:19:48 AM Elapsed: 1.42 seconds.
The package execution failed. The step failed.
so i have change some properties in our package like protectionlevel change from encrypted to dontsavesensitive. After that i have created configuration file for the package and use that configuration file. It executes the package through sql server agent
smoothly.
Thanks
Azhar Khan

Hi selfdestruct80,
According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
According to my knowledge, the package may not run in the following scenarios:
The current user cannot decrypt secrets from the package.
A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
A task or a connection manager requires that the current user account has correct permissions.
According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
/FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

Package Configuration via SQL Server For a Reporting Queue

The scenario is a reporting queue for a web application. Currently when a user queues a report it stores the parameters in a table by queue ID. When that report is set to run the database creates a dtexec command with all the parameters. We use this
method for transferring the values the user selected to the SSIS packages.
I have used SQL Server package configurations before but they are usually a single table with a distinct ConfigurationFilter column. Is it possible to take the standard table layout for the SQL Server package configuration and add another column, say
QueueID. We send the QueueID to each package at run time and use this value to filter the table to the configuration specific to that report?

Here is a better break down of the current process:
1. A user goes to the web application and selects a report/parameters.
2. This will add data to [QUEUE] and [QUEUE_PARAMETERS] tables associated by the QUEUE_ID
3. The server has a windows service which looks for reports in the [QUEUE] table in pending status and gets the next one available and calls a stored procedure with that QUEUE_ID.
4. The stored procedure puts together a dtexec command through xp_cmdshell which contains all the user parameters from the [QUEUE_PARAMETERS] table.
The purposed process is to replace the self made [QUEUE_PARAMETERS] table with the package configuration table. This means we would only have to send the QUEUE_ID via the dtexec command and not all the other parameters. The problem is that if
I add QUEUE_ID to the package configuration table I am not sure how I would reference a specific QUEUE_ID from the SSIS package configuration dynamically. There does not appear to be an expression that can be applied to the package configuration in SSIS
which means the relationship must make the ConfigurationFilter field unique, even though it is not a primary key.

SSIS package flow based on a scheduling configuration table.

I have a table called Tbl_Scheduler.
This scheduler table contains
scheduler id ,scheduler description,as shown below.
1 ,Runs between 10 th of current month and 20th of current month
2 ,Runs at last day of the month
3 ,Runs at first day of the month
Scheduler Id will come from first task(it is given in a configuration table),
second task should check this scheduler id on scheduler table and
verify whether the current run date is falling under the criteria,which is given as scheduler description.
If it is not,need to stop the package flow.
SSIS package is scheduled from SQL agent job in every 10 mins.Could you please let us know,how I can design the same.
Also please feel free to advise to change the table design.

Stopping running packages is a bad idea in general. You must specifically design a package for being stopped any time which isn't always possible, often not at all.
And running a package repeatedly in short intervals is not a SOP either.
To trigger a SSIS package run, the easiest would be via sp_start_job <name> once you have your package set up to run in Agent.
Arthur My Blog

When Deploying SSIS Packages to SQL Server using SSMS Import feature, is the package configuration file deployed at the same time?

Hello, everyone,
I have an SSIS package with a XML package configuration file. I deployed it to the sql server using the import feature in SSMS (in Stored Packages, right click MSDB, select Import, select the package to deploy in file system). My question is
Is the XML package configuration file also deployed? If so, which folder is it stored so that I can change the values in it? If not, is setting up the Configuration tab when scheduling a agent job the way to go manually bring the configuration file in?
Your help and information is much appreciated.
Regards

Thank you Arthur for your reply. I appreciate it.
A followup questions:
I used direct setting for the configuration file path on C:\. But it needs to be on D:\ on the remote server. I can't create the D:\ path because I don't have D:\ drive on my computer (I understand I could use indirect setting to change the path in the remote
server. But that's not the concern here).
My question is: since the configuration is not deployed, can I make it up by setting up the Configurations in creating the agent job step? That is, copy the configuration file to the D:\ drive on the remote server, in Configurations tab, add the configuration
file on D:\ to the configuration. Will it work? Will the package still look for the original config file on C:\? and if it doesn't find it there, will it cause any error?
Thank you in advance for your help.
Regards

To configure SSIS packages out of these SQL Server Standard, Web and Workgroup editions which is preferred?

Hi All,
To configure SSIS packages out of these SQL Server Standard, Web and Workgroup editions which is preferred?
Grateful to your time and support. Regards, Shiva

Hi Shiva,
SSIS designer and runtime, basic transforms, and data profiling tools are only supported by Standard and higher editions. Besides, some advanced SSIS adapters such as High performance Oracle/Teradata destination and Dimension processing destination adapter
are only supported in Enterprise edition. So, if you need to develop/modify SSIS packages on this server, Standard or even Enterprise editor is recommended.
Reference:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#SSIS
Regards,
Mike Yin
TechNet Community Support

Ssis 2012 configuration package wizard is hanging

Hi,
I am trying to edit the dtsconfig package xml file in SSIS 2012 VS envoirnemnt and the wizard is hanging up for minutes until I need to close VS.
Has anyone experienced this problem and what can be done to solve other than editing the XML file directly.

Hi danisroyi2 and Mike Yin Pactera
I am also experiencing this issue.
Edit an existing package configuration and click next.
It hangs on the loading properties form until you eventually (I have waited for over half an hour) have
to kill the process in task manager.
thanks

Single XML configuration file for all the SSIS packages(including parent and child packages)

Hi
I have some 16 ssis packages. source Db and destination Db for these packages are common. I am calling these child packages in a master package.
I want to use only one XML config file for this master.
How do i use same for all child packages?
and can i do it with parent package variable?

I created a master package with a variable master, and in value i have entered the configuration file path.
Hi vjp dinu,
You should create variables in the parent package to pass values to variables in each child package rather than pass the file path of the XML Configurations file of the parent package.
As Visakh mentioned, you can achieve your goal by creating corresponding variables in the parent package for each child package, and enable Package Configurations for the parent package so that you can control the values through the XML Configurations file
for the variables of the parent package.
Supposing there is a variable FilePath in child package 1, a variable ServerName in child package 2, then, we need to create two variables pFilePath, pServerName in the parent package. After configuring the Parent package variable in each child package (e.g.
mapping pFilePath to FilePath, pServerName to ServerName), you can enable XML Configurations for the parent package, and expose the value property for both pFilePath and pServerName variables. In this way, you can modify the XML Configurations file of the
parent package and the specified values will passed to the child packages.
Reference:
http://microsoft-ssis.blogspot.com/2011/06/passing-variables-from-parent-package.html
Regards,
Mike Yin
TechNet Community Support

Package Configuration Files Not loading SSIS 2012

I've migrated an SSIS 2008 project to SSIS 2012 that uses xml configuration files. When I execute the first package through the IDE, the values in the config file are not populating variables as they did in SSIS 2008. I've enabled Package Configurations
and added the config files and not sure what I could be doing wrong. Could anyone offer any suggestions.
Thanks

Someone else migrated it for me before I had vs2012 installed. So I decided I would try migrating it myself. Now the config files are loading. When I migrated it there was an option for ignore config files that was checked. I unchecked it. Could that have
been the problem?
I just have one more issue now...Whenever I open the solution, it loads the config files, but two passwords are encrypted. For some reason it tries to login to the database when I load the package. This didn't occur in SSIS 2008. Do you know of any way to
disable this? I get about 2 failures before I'm locked out of the db.
Thanks

How to pass parameters to sql agent job run configured ssis package

Hi all,
I have a big problem at my small project.
I build my SSIS package that get its variables values from a configuration file..
and when i build a SQL agent job to run this package in a schedule i set the values of variables in it .. but in run-time the package still get its parameters from the configuration file !??
any help please ?

>SQL agent job to run this package in a schedule i set the values of variables in it
One way, setup a configuration table for the package. Let the package read the values for the variables from there.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

How do I get SQL Agent to perform an FTP connection through a SSIS package?

I have created a number of SSIS packages that I am running through SQL Agent in various jobs. I have set up a Credential / Proxy for the job steps and for the most part everything runs no problem. The issue I have is with the step where I make
a connection to a FTP server and download files. In BIDS the step works fine but in SQL Agent the step times out. I presume that it has to do with the account that it is being run under but that is what I thought the Credential / Proxy was supposed
to handle (as it does for all the other steps). I am running on SQL Server 2008 R2. I have created a test job that has only one step which is to connect to the FTP server and download some text files. I have tried utilizing package configuration
files and have tried various ProtectionLevels to no avail.
Anyone have any thoughts or direction for me to take? Will continue to research and will post if I resolve this.
Thanks, Andrew

On the dev environment the ProtectionLevel is set to EncryptSensitiveWithUserKey and that is what I tried first on the prod server. Subsequently I also tried utilizing a package config file (with ProtectionLevel then of DontSaveSensitive) and have
also tried working with the ServerStorage.
For deployment I copied the relevant dtsx files to a solution on the prod server. I verified that the packages all had tested connections in the Connection Manager. I have run all the packages in the BIDS on the prod server and they all worked.
I have created a test package from scratch on the prod server to test the ftp connection. This test package runs from BIDS fine. I have set the SQL Agent file to access through the file system (no luck) and have saved the package to the SSIS Packages
and had the job step access from there (no luck either).

How to execute an SSIS package on a scheduled basis from remote server and pass in input files

I have an application server and a db server. My db server has all things SQL Server stored on it (DBMS, SSRS, SSIS, etc.) I have several nightly batch process SSIS packages (dtsx files currently) that will pickup an input file and import them
into the database. I would like to execute all batch processes from my application server as I have quite a few other ones as well that do other stuff outside of SQL Server via powershell. My question is how to do this? Is there away to execute
them remotely via DTexec.exe, should I set them up as Agent jobs and somehow pass in the file names\location (how?), create and SSIS catalog, etc.?
I need to easily be able to see if the packages execute successfully or not and if not capture the detailed information of why they failed from the remote server so I can use that to drive my process flow logic in the batch processes.

Hi Jason,
According to your description, you want to execute a package on a schedule and receive notification when package ends with error in the job.
After testing the issue in my environment, we can directly add the package in a step of a job, then add a schedule and set the Alert and Notification property in the job to achieve your requirement. For more details, please see:
Create a Database Mail in the SSMS.
Right-click the SQL Server Agent services to Enable mail profile, then select the appropriate Mail profile.
Under the Operators folder, create an operator with the correct E-mail name.
Right-click the Jobs folder to add a new job.
In the Steps pane, New a step with SQL Server Integration Services Package Type to run the package.
In the Schedules pane, New a schedule for the job.
In the Alerts pane, New an alert with SQL Server event alert, then enable Notify operators option with an operator in the Response pane.
In the Notifications pane, enable Email option with same operator and When the job fails selection.
Then when the package fails, the job would be failed and we can receive the error message in the mailbox.
Besides, please make sure the account that execute the job has correct permissions for the file, for the folder that contains the file, and for the database.
References:
Configure Database Mail – Send Email From SQL Database
How to setup SQL Server alerts and email operator notifications
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Error while executing SSIS package - Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)

Hi,
We are getting the following error when running our SSIS packages on Microsoft SQL Server 2012 R2 on Windows Server 2008 R2 SP1:
Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)
SQL Server Data Tools and SQL Server Database Engine reside on the same server.
We tried the following:
Disabling TCP Chimney Offload
Installed Windows Server 2008 SP1
Splitting our SSIS code into multiple steps so it is not all one large continuous operation
The error occurs during a BulkDataLoad task.
Other options we are investigating with the engineering team (out-sourced, so delayed responses):
Firewall configurations (everything is local, so this should not make a difference)
Disabling the anti-virus scanner
Are there other things we can try?
Any insight is greatly appreciated.
Thanks!

Hi HenryKwan,
Based on the current information, the issue can be caused by many reasons. Please refer to the following tips:
Install the latest hotfix based on your SQL Server version. Ps: there is no SQL Server 2012 R2 version.
Change the MaxConcurrentExecutables property from -1 to another one based on the MAXDOP. For example, 8.
Set "RetainSameConnection" Property to FALSE on the all the connection managers.
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/774370/ssis-packages-abort-with-unexpected-termination-message
If the issue is still existed, as Jakub suggested, please provide us more information about this issue.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Error while running SSIS package from Integration service or via Job

Hi All,
I encounter the below error while running SSIS Package from Job or integration service. However on execution completes success fully while running from data tools. The issue occurs after migration to 2012 from 2oo5 dtsx. PFB the error.
SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by
the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
A buffer failed while allocating 10485760 bytes.
The system reports 26 percent memory load. There are 206110765056 bytes of physical memory with 150503776256 bytes.
free. There are 2147352576 bytes of virtual memory with 185106432 bytes free. The paging file has 208256339968 bytes with 145642921984 bytes free.
The package also runs successfully from other servers. This happens only in one of our server.seems like issue with some sql configuration.

Hi ,
Are you running using SQL Agent Job and Data tools on same server or different?
If it is executing fine using Data tools and failing with Job it might be User credentials issue.Try
to run Job with your credentials by using proxy .
Regards,
Prathy
Prathy K

SSIS package configurations

Similar Messages

Maybe you are looking for