June 15, 2017 at 9:17 am
I need to create and attach a password to protect the Excel files generated by SSIS package, and I found some guidance on SQL server Central (http://www.sqlservercentral.com/articles/Integration+Services+(SSIS)/71222/)
But it talks about creating a C# console application - which I don't have the resources to do this nor am I able to install any new software. I have Visual Studio 10.
Is there anyway I can password protect files generated by SSIS packages with the existing resources I have access to.
Much appreciated.
Susan
June 15, 2017 at 9:21 am
susan.evans10 - Thursday, June 15, 2017 9:17 AMI need to create and attach a password to protect the Excel files generated by SSIS package, and I found some guidance on SQL server Central (http://www.sqlservercentral.com/articles/Integration+Services+(SSIS)/71222/)
But it talks about creating a C# console application - which I don't have the resources to do this nor am I able to install any new software. I have Visual Studio 10.
Is there anyway I can password protect files generated by SSIS packages with the existing resources I have access to.Much appreciated.
Susan
Do you have the option of about calling 7-Zip (or similar) at the end of the job to zip the files up and password protect the zip file? Example here.
June 16, 2017 at 2:03 am
It looks like I have 7 zip file manager which I assume is slightly different and can't use that???
Can I do it within Visual Studio or within my SSIS package - perhaps have my password in a different file which it reads?
June 16, 2017 at 6:14 am
susan.evans10 - Friday, June 16, 2017 2:03 AMIt looks like I have 7 zip file manager which I assume is slightly different and can't use that???Can I do it within Visual Studio or within my SSIS package - perhaps have my password in a different file which it reads?
The tasks I recommend for you are as follows. I suggest that you do them incrementally ... get one done and working and then move to the next:
1) Get used to working with the 7-Zip command line, so that you can do what you want to do outside of SSIS.
2) Add an Execute Process (EP) task to your SSIS package which emulates the command line you have crafted in (1), and test. You may have to resolve some permissions issues at this point (a common theme when working with external files in SSIS)
3) Create a 'sensitive' parameter in your package and save the password there. Use this parameter in your EP task. Once in place, you can use a sensitive SSISDB environment variable to securely pass the value of the password at runtime.
Good luck.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy