Hi,
I fought with the permissions in SQL Server 2005 to get the permissions correct to execute an SSIS package. Eventually I ended up creating a credential with my NT login name, like domain\Paul. I also had to type in and save my NT login password. All is working perfectly now.
However, when I get prompted in 30 days to change my NT password, looks like I will also need to change it in SQL Server as well, so that my automated jobs continue to execute. Is there some other way to set up the credential so that I won't need to change my password inside that credential to match my network domain password?
I tried every other way I could think of and the only way to get the proper permissions to execute my file reading/writing SSIS packages was to use my NT login and password.
Thanks for any help,
Psul
I fought with the permissions in SQL Server 2005 to get the permissions correct to execute an SSIS package. Eventually I ended up creating a credential with my NT login name, like domain\Paul. I also had to type in and save my NT login password. All is working perfectly now.
However, when I get prompted in 30 days to change my NT password, looks like I will also need to change it in SQL Server as well, so that my automated jobs continue to execute. Is there some other way to set up the credential so that I won't need to change my password inside that credential to match my network domain password?
I tried every other way I could think of and the only way to get the proper permissions to execute my file reading/writing SSIS packages was to use my NT login and password.
Thanks for any help,
Psul