Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Import/Export Data password not saving Expand / Collapse
Posted Monday, July 13, 2009 8:19 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 11, 2011 5:27 AM
Points: 30, Visits: 96
I have created an data export package using the SQL Export wizard in 2005. The Source DB is located at our Data center and the Destination DB is located on the local network. We use SQL server user in order o connect to the Source DB and have given this user access to the DB we need to import.

During the creation of the SSIS package we save this package into the file system on a 3rd server also located on the local network and then we import the package into integration services engine on the same server. We've also created a Job on that server to execute the package.

The problem I seam to be having is that after running the package it fails indicating that NO PASSWORD has been given for connecting the remote server at our data center. The work around has been executing the package directly in Integration Services HOWEVER prior to running the package I need to supply a password test in the SourceConnection string and then execute immediately from Execute Package Utility.

After executing the package, exiting out of the utility and then re-entering the utility the password has not been saved. I have also explicitly saved the password in the Job Configuration Datasource Tab the same way I would do it in the Utility but after running the job I get the same result, "NO PASSWORD PROVIDES FOR SOURCE DATA"

Lastly I opened the package up in Visual Studio and added the password manually selected the "Save Password" check box, saved the file, re-imported package back into Integration Services from File and re-ran package and I still get the error. Why won't the password save???
Post #752074
Posted Monday, July 13, 2009 9:52 AM

Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 9:25 AM
Points: 1,071, Visits: 2,869
It sounds like you may have your SSIS package protection level set to "Don't Save Sensitive", which will not store any passwords and will prompt each time. You should set this to some other selection - most would recommend "Encrypt Sensitive with Password".

See the following discussion for more info:


Tim Mitchell, Microsoft Data Platform MVP
Data Warehouse and ETL Consultant

Post #752178
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse