SSIS Package Creation in C# 2008 vs 2012

Hi folks
If I run the following code:
Package package =
new Package();
and I have 2008 and 2012 installed which package version does it create?
Presumably depends on the API's and namespaces I reference?
Thanks
shaun

Hi Shaun,
Yes you are correct it depends on which dll you have referenced in your code.
http://microsoft-ssis.blogspot.in/2012/09/call-ssis-2012-package-within-net.html
Thanks, Dilkush Patel Microsoft SQL Developer Support Microsoft Corporation

Similar Messages

Getting error after enabling the Transaction in SSIS package in Windows Server 2008 R2 Standard machine

Hi,
I created a package with "Execute SQL Task and Data Flow Task". I am able to execute successfully in my server having
"Windows Server 2008 R2 Standard" Operating System.
But after enabling the Transaction in my SSIS Package I am not able to execute it. It is giving error. The same package is running in my local machine with Transaction enabled on
Windows 7 Operation System.
The error which I got in my server after enabling the Transaction is
"The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D025
"The partner transaction manager has disabled its support for remote/network transactions.". End Error "
I search with this error message in google and found some solutions in the following links
http://social.msdn.microsoft.com/Forums/en-US/7172223f-acbe-4472-8cdf-feec80fd2e64/the-partner-transaction-manager-has-disabled-its-support-for-remotenetwork-transactions
http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx
http://support.microsoft.com/kb/817064
But none of the above solution is not working. Kindly help me to resolve this issue.
Thanks in Advance.
Sridhar

Hi Sridhar,
Please compare the DTS settings on the Windows 7 computer and the Windows Server 2008 R2 computer and make sure they are identical. Make sure the “Allow Inbound” and “Allow Outbound” options are check, and pay attention to the authentication mode as
well.
Besides, make sure both Distributed Transaction Coordinator (TCP-In) and Distributed Transaction Coordinator (TCP-Out) rules in Firewall are enabled.
If the issue persists and there are any security/anti-virus software, temporarily disable the security/anti-virus software and check the issue again.
Regards,
Mike Yin
TechNet Community Support

Error in SSIS Package in SQL Server 2008 R2

Dear All,
I am getting below error in SSIS Package.
[OLE DB Destination [31]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "The statement has been terminated.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >,
>= or when the subquery is used as an expression.".
The SSIS package reads .xml file from a folder and then mapped to insert values in SQL table from there one trigger writtern on table to update other tables.
Pld guide me cause of the issue
-- Kind Regards Sandeep

Dear All,
I am getting below error in SSIS Package.
[OLE DB Destination [31]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "The statement has been terminated.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when
the subquery is used as an expression.".
The SSIS package reads .xml file from a folder and then mapped to insert values in SQL table from there one trigger writtern on table to update other tables.
Pld guide me cause of the issue
-- Kind Regards Sandeep
Query should return only one value. Instead it is returning more than one value. Check the query result in ssms.
Thanks.
- please mark correct answers

Calling SSIS package from DTEXEC in SQL Server 2012

Hello,
I have a package called test.dtsx developed in SSIS vs 2010 (project deployment model). It has two project parameters one is db connection (string) and one is classnumber(string). This package has been deployed as file system and in SSISDB. I want to
assign the following values to the project parameters
$Project::DBConnection - Data Source=localhost;User ID=User;Password=password;Initial Catalog=testdb;Provider=SQLNCLI11.1;Persist Security Info=True;Auto Translate=False;
$Project::Classnumber - 10
What is the syntax to call this package from dtexec passing values for parameters
1. as a file system deployment
2. as a package in SSIS db(catalog)
thanks

http://msdn.microsoft.com/en-ca/library/hh231187.aspx has an example
Dtexec /isserver “SSISDB\MyFolder\MyProject\test.dtsx” /server “.” /parameter $Project::DBConnection;thevalue /parameter anotherparam(int32);12
Arthur My Blog

SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

I am working in a Product based company.
We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
I have used "Script Component" in my package.
We will take only DTSX package file to the customer places and run using SQL Agent Job daily.
Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
Who are all(Customer Environments) using SQL 2012, I am facing the below issue
The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Still the same package is running fine for some of the customers having SQL 2012.
I am getting the above error only for few customers.
Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

Hi Katherine,
I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
Here is my Simple .net code
/* Microsoft SQL Server Integration Services Script Component
* Write scripts using Microsoft Visual C# 2008.
* ScriptMain is the entry point class of the script.*/
using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
public override void PreExecute()
base.PreExecute();
Add your code here for preprocessing or remove if not needed
public override void PostExecute()
base.PostExecute();
Add your code here for postprocessing or remove if not needed
You can set read/write variables here, for example:
Variables.MyIntVar = 100
int counter = 0;
public override void Input0_ProcessInputRow(Input0Buffer Row)
if (counter == 0)
counter = Convert.ToInt32(Row.JurisCount);
Row.JurisKey = counter;
counter = counter + 1;
PAVAN MSBI

Run sql 2008 ssis package into sql server 2012 machine

Hello,
I have created a ssis package in sql server 2008 and use a job to execute it pointing to databaseA. works fine.
Then, I place that package into a sql server 2012 machine and use a job to execute it in the same database, databaseA.
The error I get is something like:
can not use the old version in the new version machine.
Is this really the case or am I doing something wrong please?

Hi Arkiboys,
Arthur is right that the error occurs because the SSIS 2008 package cannot be upgraded to SSIS 2012 package. When the SSIS 2008 package is called by SSIS 2012 dtexec utility tool, the package will be upgraded temporarily and the changes won’t be saved. Since
your current SSIS 2008 package cannot be upgraded automatically, you can create the package from scratch in SSDT installed by SQL Server 2010. Another option isto open the SSIS 2008 package in SSDT or add the package to a SSIS 2012 project, then the upgrade
will be performed automatically. Then, you can check the error message during the upgrade, which may help you to find the tasks/components that cause the upgrade failure. In this way, you can remove the tasks/components in question from the SSIS 2008 package
and then upgrade the package, and then add the tasks/components in question in SSDT 2010.
Regards,
Mike Yin
If you have any feedback on our support, please click
here.
Mike Yin
TechNet Community Support

Getting error code 1 when calling SSIS package from a stored procedure (SQL Server 2008 R2)

Hello,
I am trying to execute a SSIS package from SQL Server 2008 R2 stored procedure but getting error code 1 (as per my knowledge, error code description is as below:
0 The package executed successfully.
1 The package failed.
3 The package was canceled by the user.
4 The utility was unable to locate the requested package. The package could not be found.
5 The utility was unable to load the requested package. The package could not be loaded.
6 The utility encountered an internal error of syntactic or semantic errors in the command line.
Details:
I have a stored procedure named "Execute_SSIS_Package" (see below sp) which executes 'Import_EMS_Response' SSIS package (when I execute this package directly from SQL Server BID it works fine it means package itself is correct) and calling
it from SQL as:- EXEC Execute_SSIS_Package 'Import_EMS_Response'.
Here I receives error code 1.
Can anyone help me to resolve this issue please?
Thanks in advance!
CREATE PROCEDURE [dbo].[Execute_SSIS_Package]
@strPackage nvarchar(100)
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
DECLARE @cmd VARCHAR(8000)
DECLARE @Result int
DECLARE @Environment VARCHAR(100)
SELECT @Environment = Waarde
FROM Sys_Settings
WHERE Optie = 'Omgeving'
--print @Environment
SET @strPackage = '"\W2250_NGSQLSERVER\BVT\' + @Environment + '\' + @strPackage + '"'
SET @cmd = 'dtexec /SQL ' + @strPackage + ' /SERVER "w2250\NGSQLSERVER" /Decrypt "BVT_SSIS" /CHECKPOINTING OFF /REPORTING E'
--print @cmd
EXECUTE @Result = master..xp_cmdshell @cmd, NO_OUTPUT
--print @Result
END

It has something to do with the security.
E.g. cmdshell is not enabled or the caller has not rights over the package.
There could be a syntax error, too.
I suggest you make the package runnable off a SQL Agent job then trigger the job from the stored proc with
sp_start_job <job name>
Arthur
MyBlog
Twitter

SQL 2012 SSIS package runs from the command line (dtexec.exe) and completes right away ...

Hi
I’m upgrading our SSIS packages from SQL 2005 to SQL 2012 .
Everything is working fine in Visual Studio, but when I’m submitting dtexec.exe it’s finishing right away in the command line (the actual execution takes long time).
It looks to me that as the return code doesn’t pass properly.
As I have depending tasks how I can make sure all jobs will be executed in the proper order.
(We never had this issue in SQL 2005)
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn>dtexec.exe /ISSERVER "\"\SSISDB\Direct_Prod\Direct_SSIS_Package
\DD_Load_Customer.dtsx\"" /SERVER TORSQLSIS01 /ENVREFERENCE 2
Microsoft (R) SQL Server Execute Package Utility
Version 11.0.2100.60 for 32-bit
Copyright (C) Microsoft Corporation. All rights reserved.
Started: 10:21:55 AM
Execution ID: 21138.
To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report
Started: 10:21:55 AM
Finished: 10:21:56 AM
Elapsed: 0.766 seconds

As per MSDN /ENVREFERENCE argument is used only by SQL Server Agent
see
https://msdn.microsoft.com/en-us/library/hh231187.aspx
below part is what it says
/Env[Reference] environment reference ID
(Optional). Specifies the environment reference (ID) that is used by the package execution, for a package that is deployed to the Integration Services server. The parameters configured to bind
to variables will use the values of the variables that are contained in the environment.
You use /Env[Reference] option together with the /ISServer and the /Server options.
This parameter is used by SQL Server Agent.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Can't change the connection string of SSIS package with derived columns?

We upgraded SQL server 2008 to 2012, copied and converted all SSIS packages from Visual Studio 2008 to 2010. When I opened a package in VS 2010 and tried to change the connection string, in the local connection managers, if the data source is another
SSIS package B(.dtsx file) with derived columns, I can't change the connection string of package B. When I opened the file connection manager editor for package B and tried to locate a dtsx file in another location, saved the change, reopened the project.
Package B still pointed to previous file. Other packages without derived columns work fine. Any thoughts?

We are using the package deployment model and refer to other packages in the same project. If
we changed the path of package B (with derived columns) to "D:\Visual Studio 2010\xxxx", and refer it in package A, in the A's connection manager, the connection string of package B is still its previous location "D:\Visual
Studio 2008\xxxx". When we ran the package A in the SQL server agent, the data source is still
"D:\Visual
Studio 2008\xxxx", so how can I change it to "D:\Visual
Studio 2010\xxxx"? Why has the package C (without derived columns) no such problem? thanks.

How Can I Kill Excel.exe Process After finish my Execution of SSIS Package in Sqlserver2008r2

Hi !,
am new for c# and SSIS Package Creation , I am Trying to Read Excel file, and load the value into Sqlserver using SSIS package . My Problem is , After Execution of SSIS package Still Running EXCEL.exe Process in my server. i need to
kill that process . I post my Code Exactly where am release my excel file object , please guide me where am going to wrong?
Server Configuration
OS:windows7
SqlServer :2008r2
Framework:3.5
please give me some suggestion to correct my error .
Here is My Code:
Microsoft.Office.Interop.Excel.Application xlApp;
Microsoft.Office.Interop.Excel.Workbook xlWorkBook;
Microsoft.Office.Interop.Excel.Worksheet xlWorkSheet;
var missing = System.Reflection.Missing.Value;
xlApp = new Microsoft.Office.Interop.Excel.Application();
xlWorkBook = xlApp.Workbooks.Open(filename, false, true, missing, missing, missing, true, Microsoft.Office.Interop.Excel.XlPlatform.xlWindows, '\t', false, false, 0, false, true, 0);
xlWorkSheet = (Microsoft.Office.Interop.Excel.Worksheet)xlWorkBook.Worksheets.get_Item(1);
Microsoft.Office.Interop.Excel.Range xlRange = xlWorkSheet.UsedRange;
Array myValues = (Array)xlRange.Cells.Value2;
int vertical = myValues.GetLength(0);
int horizontal = myValues.GetLength(1);
System.Data.DataTable dt = new System.Data.DataTable();
bool isNameRead = false;
// get header information
for (int i = 1; i <= horizontal; i++)
string cellValue1 = "";
object cellObj = myValues.GetValue(1, i);
if (cellObj != null)
cellValue1 = myValues.GetValue(1, i).ToString();
if (cellValue1 == "Name")
if (!isNameRead)
dt.Columns.Add(new DataColumn(cellValue1));
isNameRead = true;
else
dt.Columns.Add(new DataColumn(cellValue1 + 1));
isNameRead = false;
else
dt.Columns.Add(new DataColumn(cellValue1));
// Get the row information
for (int a = 2; a <= vertical; a++)
//string cellrowvalue = "";
string isemt = "";
object[] poop = new object[horizontal];
for (int b = 1; b <= horizontal; b++)
isemt =(string) myValues.GetValue(a, b);
if (isemt != null)
poop[b - 1] = myValues.GetValue(a, b);
DataRow row = dt.NewRow();
row.ItemArray = poop;
dt.Rows.Add(row);
xlWorkBook.Close(true, missing, missing);
xlApp.Quit();
releaseObject(xlWorkSheet);
releaseObject(xlWorkBook);
releaseObject(xlApp);
return dt;
releaseObject
private void releaseObject(object obj)
try
System.Runtime.InteropServices.Marshal.ReleaseComObject(obj);
obj = null;
catch (Exception ex)
obj = null;
MessageBox.Show("Unable to release the Object " + ex.ToString());
finally
GC.Collect();
GC.WaitForPendingFinalizers();
GC.Collect();
GC.WaitForPendingFinalizers();
Thanks
Parthasarathi Purushothaman

Why are you programmatically opening an Excel sheet in C# instead of using the DataFlow task with an Excel input?
Since your task is programmatically starting Excel via "new Microsoft.Office.Interop.Excel.Application();", it is your responsibility to stop it.
Please see "Quit":
http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel._application.quit(v=office.15).aspx

Error connecting to Oracle from when running SSIS Package on Windows 64-bit

Hi.
I have an SSIS (SQL Server Integration Services) Package that reads a view on Oracle and loads data into table in SQL Server 2005. This is on a Windows 2008 Server (64-bit). SQL Server 2005 with SP3. Oracle Client 11g (32 bit & 64 bit) Runtime Version installed on server. The server has been rebooted since installing OracleClient.
I get the following error when run as a SQLAgent job 64 Bit (Execution type SQL Server Integration Services Package)...
Started: 9:29:24 AM
Error: 2010-01-04 09:29:25.37
Code: 0xC0202009
Source: SADM_CURR_Address_and_Cell_Phone-Oracle Connection manager "Oracle/PeopleSoft"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
End Error
Error: 2010-01-04 09:29:25.37
Code: 0xC020801C
Source: DFT-Oracle to SS2005 OLE DB Source [1]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Oracle/PeopleSoft" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Error: 2010-01-04 09:29:25.37
Code: 0xC0047017
Source: DFT-Oracle to SS2005 DTS.Pipeline
Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.
End Error
Error: 2010-01-04 09:29:25.37
Code: 0xC004700C
Source: DFT-Oracle to SS2005 DTS.Pipeline
Description: One or more component failed validation.
End Error
Error: 2010-01-04 09:29:25.37
Code: 0xC0024107
Source: DFT-Oracle to SS2005
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 9:29:24 AM
Finished: 9:29:25 AM
Elapsed: 1.108 seconds
When I execute this same exact package as a SQLAgent job 32-bit (type Operating System CmdExec) it runs successfully. When I run the package using the Execute Package Utility, it runs successfully. When I am editting the package in BIDS I can connect to Oracle. For both 64 and 32 bit, I use a dtsconfig file which specifies the Oracle connection string and password.
Someone mentioned on another forum that maybe there is no Oracle ODBC driver for 64-bit Windows. I would assume that the OracleClient 64-bit would include that.
I hope I have included all info needed. Please let me know if you may have a resolution to this problem.
Thanks.
John

I was trying to transfer data from oracle to sql server 2008 on a daily basis.
I have very hard time connecting to oracle from ssis package on windows server 2008. I am almost dead and cannot find any help. i was able to connect to oracle using import/export 64 bit feature of SQL Server 2008 using Oracle provider for OLEDB. But I am not sure why the same does not work with BIDS?
Here's the environment info:
1. Oracle Client 10g
2. SQL Server 2008
3. Windows Server 2008
Appreciate your help. Please save me.
Thanks,

Deadlock error in SSIS package

I have a SSIS package in SQL Server 2008. It has several tasks running in parallel. These jobs are Data Flow tasks and Script tasks. All these tasks are inserting/updating data on common tables. All the tasks are doing insert/update on very large data. Everything
was working fine but a few days ago the package started failing with following error.
" Transaction (Process ID 67) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim"
Kindly Suggest.

Can you provide more info on the deadlock, if you turn on the
Traceflag 1222. This traceflag is responsible for printing detailed resource information for deadlocks on SQL Server. Or run SQL Server Profiler with enable event(Locks ->
Deadlock graph).
Thanks
Saravana Kumar C

What is the most common way of deployment of SSIS package?

Hi everybody,
I am new to SSIS. I have created an SSIS package in development server. I want to deploy it to production server. What is the most common and efficient way of deployment? Please let me know the procedure in details.
Thanks in advance.
Regards,
Anujit Karmakar
Anujit Karmakar Sr. Software Engineer

Hi Anujit,
SSIS deployment is nothing but just to copy the .dtsx files from DEV to PROD. (Either file system or SQL Server)
File system deployement is the common way of SSIS deployment
1. File system deployment using manifest file
http://sivasqlbi.blogspot.in/2012/05/ssis-step-by-step-process-of-creating.html
2. SQL Server deployment using manifest file
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
3. By using Command line
http://www.mssqltips.com/sqlservertutorial/215/command-line-deployment-tool-for-ssis-packages/
If you are working on SQL Server Data Tools (2012), then you need to go through below article
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-1-of-2/
-Vaibhav Chaudhari

How to Run 2012 SSIS packages on 2008R2 Version

HI Friends,
I have scheduled a job to run 2012 SSIs packages on 2008R2. I am getting this error can you please Give any ideas how can I run them without converting!
ERROR Is :
Package migration from version 6 to version 3 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number."

Hello,
There is backward compatibility in SSIS but no forward compatibility, meaning, when 2008 R2 is developed they were aware of all versions less than 2008 R2 and included execution scenarios , this is backward compatibility
while 2008 R2 is being developed , 2012 is not yet developed. so we cannot execute a 2012 package on 2008 R2 Server where vice versa is possible
Correct.
The "backwards compatibility" is implemented by SSIS upgrading older versions of packages to the current version of SSIS when executing. If the upgrade fails, you're out of luck.
MCSE SQL Server 2012 - Please mark posts as answered where appropriate.

Execute the SSIS packages (2008 version) using SQL job 2008

We need to execute the SSIS packages (2008 version) using SQL job Please help with details information how to execute it.
1.Protection level of the SSIS packages.
2.Configuration File (Curently using XML file)
3.Please provide details how to create Credential (Windows User etc) Do we need to create windows cred explicitly to run the Job etc..
4.Please provide details for creating Proxy.
5.How can we configure the xml file since the xml is reading from local box but when the package is moved from developement box to production box
then the local drive might not be mapped with Production box .
6.Roles that need to be tagged for the Proxy/Credential.
7.Which is the best and safest way to execute ssis packages either msdb deployment or filesystem deployment and other necessary details.

Hi,
If you want to Execute your SSIS package using SQL job then best solution is to first deploy your Package
either using msdb deployment or filesystem deployment.The simplest approach to deployment is probably to deploy to the file system.
So, here is the deployment steps;
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 or to an instance of SQL Server.
you can use below link also;
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
After that you need to Schedule package using SQL Agent then Have a look at the following link. It explains how to create an SQL job that can execute an SSIS package on a scheduled basis.
http://www.mssqltips.com/sqlservertutorial/220/scheduling-ssis-packages-with-sql-server-agent/
Deployment in msdb deployment or filesystem deployment has there own merits and demerits.
For security point of view msdb deployment is good.
it provides Benefits from database security, roles and Agent interaction
Protection Level;
In SQL Server Data Tools (SSDT), open the Integration Services project that contains the package.
Open the package in the SSIS designer.
If the Properties window does not show the properties of the package, click the design surface.
In the Properties window, in the Security group, select the appropriate value for the
ProtectionLevel property.
If you select a protection level that requires a password, enter the password as the value of the
PackagePassword property.
On the File menu, select Save Selected Items to save the modified package.
SSIS Provide different Protection levels;
    DontSaveSensitive
    EncryptSensitiveWithUserKey
    EncryptSensitiveWithPassword
    EncryptAllWithPassword
    EncryptAllWithUserKey
    ServerStorage
For better undertsnading you can use below link;
http://www.mssqltips.com/sqlservertip/2091/securing-your-ssis-packages-using-package-protection-level/
Thanks

SSIS Package Creation in C# 2008 vs 2012

Similar Messages

Maybe you are looking for