July 10, 2017 at 3:07 pm
Why does my SSIS package run as a job only when the creator of the package matches the account used to run the SQL agent service?
There's gotta be another way!
July 10, 2017 at 4:23 pm
Could you provide more information such as the error and information from your logs?
I do not have that problem. I have my SSIS packages run as a job where sa is the owner (as I've read problems can occur otherwise). But prior to that, we did have some jobs running as one of our DBA's (me) because I forgot to change it. Jobs ran no problem until the DC was rebooted and SQL couldn't authenticate.
If you post the error instead of just saying "it doesn't run", we can be more help.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply