DSN ODBC pwd not saved when SSIS package imported
SQL Server 2005 SP2 (Windows 32bit version)
Implemented and FULLY tested a SSIS package with BIDs.
This package uses a Data Reader object using a ODBC data source with a stored username (uid) and password (pwd).
These are saved with the package locally.
I then import the package directly in to SQL Server.
I then create a scheduled SQL Agent job to run this package daily. When I look at the Data Source tab which lists all data sources this package uses the password is not listed.
I then ran this job and as I expected it did not run because of the missing password.
If I modify the data source within the job it lets me but it doesn't save the password.
The DSN in ODBC Administator actually saves the password in the registry. Why doesn't SQL Server store the encrypted password.
I needs this to work otherwise my project will fail.
Any ideas anyone?
Thanks,
Regards,
Richard.
SQL Server 2005 SP2 (Windows 32bit version)
Implemented and FULLY tested a SSIS package with BIDs.
This package uses a Data Reader object using a ODBC data source with a stored username (uid) and password (pwd).
These are saved with the package locally.
I then import the package directly in to SQL Server.
I then create a scheduled SQL Agent job to run this package daily. When I look at the Data Source tab which lists all data sources this package uses the password is not listed.
I then ran this job and as I expected it did not run because of the missing password.
If I modify the data source within the job it lets me but it doesn't save the password.
The DSN in ODBC Administator actually saves the password in the registry. Why doesn't SQL Server store the encrypted password.
I needs this to work otherwise my project will fail.
Any ideas anyone?
Thanks,
Regards,
Richard.