Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

passwords and package encryption Expand / Collapse
Author
Message
Posted Thursday, January 24, 2013 9:22 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, July 28, 2014 10:49 AM
Points: 246, Visits: 790
Due to unicode "upgrade", I'm looking at redoing about 20 packages. I use the wizard to generate the package. This is where I choose to encrypt sensitive data with a package password. Once it's done, sometimes I need to add a step or two so then I reset the sql connection password (click save), set encryption on the package to password and type the password again. Then, I setup the SQL AGent job in which I have to type the package password and then I have to click on the data sources and for the SQL connection I enter ;password=myserverpassword. Of course, sometimes there's a typo or something does not register right and the job fails when it runs, so I have to go back into package and double check sql connection password and password encryption password (whew).

To redo these, what is the best method with encryption or is there something else?



Post #1411206
Posted Monday, January 28, 2013 5:46 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 3:55 PM
Points: 13,357, Visits: 10,222
If you don't have a lot of connections, I would set-up a configuration table and store the username and password there.

That way you won't have to use a password to protect your package and so you can't make a typo




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1412372
Posted Monday, March 11, 2013 2:38 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 26, 2013 6:20 AM
Points: 3, Visits: 36
Koen Verbeeck (1/28/2013)
If you don't have a lot of connections, I would set-up a configuration table and store the username and password there.

That way you won't have to use a password to protect your package and so you can't make a typo


How do You read The config table? And use them in your connections?
Do you have ore can lead me to a sample ?

Post #1429477
Posted Monday, March 11, 2013 2:46 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 3:55 PM
Points: 13,357, Visits: 10,222
Jordan2000 (3/11/2013)
Koen Verbeeck (1/28/2013)
If you don't have a lot of connections, I would set-up a configuration table and store the username and password there.

That way you won't have to use a password to protect your package and so you can't make a typo


How do You read The config table? And use them in your connections?
Do you have ore can lead me to a sample ?



This article contains all the info you need:
Understanding Integration Services Package Configurations




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1429480
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse