You can use the msdb.dbo.sp_start_job procedure to start the job. In SSIS create a new SQL task and run the job wherever required

exec msdb.dbo.sp_start_job @job_name = 'JobName'

For more information about sp_start_job please refer MSDN

Sql server Destination cannot be used in packages that access a SQL Server database on a remote server. Instead use the OLEDB destination.

Things to note for SQL Server Destination

a. It offers the same speed as the Bulk Insert Operation.
b. It does not support Error Output.

For more information please check msdn

a. When you Encrypt the Data in SSIS make sure you Encrypt in Batches(i.e dont encrypt the same data again).
b. The datatypes should be valid for the Encrypted Content and should have enough space to store it(I used nvarchar(max))

Below is a small Example of the Encryption Process:

Encrypting the Database

use EncryptionTest

--Create a Master Key by Encryption
create master key Encryption by password = 'Sql5erver'

--Create the Certificate
create certificate testcert with Subject = 'Testing the Symmetric Encryption'

--Create the Symmetric Key with Algorithm and Encrypt it with the certificate
create Symmetric Key testkey with algorithm =  AES_256 encryption by certificate testcert;

Sample Tables and Data

create Database Encryptiontest
go

create table Source
(
	UserID int
	,[Name] varchar(100)
	,Password varchar(max)
)
go

insert into Source
select 1,'Vivek','Sqlserver007'
union
select 2,'Jermey','MungingData'
union
select 3,'Marcus','SirMarcus'
union
select 4,'Cesare','Berlusconi'
go

create table EncryptedData
(
	userID int
	,[Name] varchar(100)
	,EncryptedPassword nvarchar(max)
	,Logid int
)

go

Procedure for Encryption

The Detailed Syntax for EncryptbyKey is given in this MSDN article

create procedure EncryptData
(
	@Logid int
)

as

Open Symmetric Key Testkey Decryption by Certificate TestCert

update EncryptedData
set EncryptedPassword = ENCRYPTBYKEY(Key_guid('testkey'),EncryptedPassword) where Logid = @Logid

Now Coming to the SSIS Task. I have used the Logid as the variable which controls the records to be encrypted in every flow(i.e the Log id changes for every iteration of the dataflow task). Once the records are transferred to the Destination table EncryptedData the procedure Encryptdata @Logid is executed.

Variables and the DataSourcetask

DataFlow task and Derived Column

How to Decrypt the Data?

Once the Data is encrypted the table is displayed as follows

For Decryption the End user should have the following permissions
Grant Control on Certificate
Grant View Definition on Symmetric Key

Following is the way to Decrypt. You need to open the Symmetric key to Decrypt it.

Open Symmetric Key TestKey Decryption by Certificate TestCert

select UserID,[name],CAST(DecryptByKey(EncryptedPassword) as nvarchar) as Password from
EncryptedData
 

The following are the DMV’s(Dynamic Management Views) that can be used for Encryption

--Checking the Symmetric keys
select * From sys.symmetric_keys

--Checking the certificates
select  * from sys.certificates

--Checking for any openkeys
select * From sys.openkeys

There are some good articles on Encryption that may be useful to you in future.

Encryption HierArchy
http://blogs.technet.com/keithcombs/archive/2005/11/24/sql-server-2005-data-encryption.aspx

I have a simple Dataflow task(as shown below) that gets the data from a table and exports it in a Tab delimited text file.

The Data Flow Task

I have set up a following variable called ServerName where I can change the value dynamically on the Connection String.

Variable Server Name

To configure the ConnectionString to use the Variable name dynamically at RunTime we need to configure Dimensions. This is how its done.Right Click on the Connection String and click properties(or click F4 by highlighting Databaes connection)

Database Connection Properties

In the Properties section click on the Expression for configuring nd also setting the Servername settings as below.

Expressions_Connection_Properties

Select ServerName

Configure Value as ServerName

Click Ok twice and the expressions are now configured. The best way to check it is to use the Bidshelper. (www.codeplex.com/BidsHelper) In the below diagram as you notice the Pink colour on the edge of the Connection String Icon which represents that the connection is configured via Expression.

The above example should give you a good example on how to configure Connection Strings using Expressions. Just keep commenting .

So whats the solution?
Append set ANSI_WARNINGS OFF on the beginning of the sql statement.

When using the same in SSIS packages the Packages may fail.The Output Window may indicate that there is already a OLEDB destination exported which in this case is the error message.

An OLE DB record is available. Source: “Microsoft SQL Native Client” Hresult: 0x00040EDA Description: “Warning: Null value is eliminated by an aggregate or other SET operation.”

So use set ANSI_WARNINGS OFF