EncryptSensitiveWithUserKey - means that the user that creates the package
encrpyts the sensitive details and effectively only they can decrpyt them.
use them outside of the package. They are a beautiful addition to SSIS
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqltut9/html/005218ab-8dd5-48e9-a185-6bc60cd43a7a.htm
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/extran9/html/d4b073c4-4238-41fc-a258-4e114216e185.htm
"carolus.holman" <carolusholman@discussions.microsoft.com> wrote in message
news:BE0B8439-0046-4553-B070-3F2DEB1E3FE2@microsoft.com...
> It is set at <default> EncryptSensitiveWithUserKey. What I need to know
> is,
> what is the best way to do this?
>
> I ended up going into the SQL Job Agent, selecting the step and placing
> the
> password into the Connection string under the Job Properties/DataSources
> tab.
> It still didn't save the info, but now the package runs...I am not
> familiar
> with writing configuration files. BOL has not been very helpful in this
> area.
>
>
>
> "Allan Mitchell" wrote:
>
>> What is the package Protection Level?
>>
>> This will encrypt/Not Save sensitive information in the package.
>>
>> You can pass in the U and P to the Connection Manager through
>> configurations.
>>
>>
>> --
>>
>>
>> Allan Mitchell
>>
www.SQLDTS.com >>
www.SQLIS.com >>
www.Konesans.com >>
>>
>> "carolus.holman" <carolusholman@discussions.microsoft.com> wrote in
>> message
>> news:0B1578E8-AFBC-43F0-AAAA-46D3150CE500@microsoft.com...
>> >I am using Integration services to move some data from an Oracle DB to a
>> > SQL2005 DB. When I run the package from my DEV machine everything works
>> > splendid, however when I deploy the package, the Oracle connection
>> > fails,
>> > with a NULL Password. I have tried DSN, OLEDB Connections. When I edit
>> > the
>> > Connection String in the package manager it works, but it does not save
>> > the
>> > edit for unattended execution (Scheduled Jobs). I have scoured looking
>> > for
>> > an
>> > answer to this but haven't found one. Anyone have any idea?
>> >
>> > Thanks
>>
>>
>>
