Ugh! I screwed up. I’m going to tell you guys about it and beg your forgiveness.
What I did: I gave out some bad info in my session on SSIS in Columbia, SC this past weekend.
What I said: I said that when an SSIS package is executed using a SQL Server Agent job, that the Service Account under which SSIS is running under requires all of the necessary permissions (file, etc). I said that the Service Account for the agent also needs these permissions.
What’s wrong with that: The account under which SSIS runs under is not a player in jobs executed by the Agent. Only the Service Account that the Agent uses matters. If giving that account the necessary permissions is just not an option, then you need to execute the Agent job under a proxy account. Here is an excellent post covering this topic.
How I got screwed up: I got confused with this a few years ago. I had a file permissions error with an Agent job executing an SSIS package and could have sworn that I resolved it by giving the SSIS service account the necessary permissions.
What must have happened: Looking back, the agent must have been running under the same service account that SSIS was running under.
So there it is, my mea culpa. If you saw my session and are reading this, I apologize. Please tell anyone who was with you about my error, so that we can nip this bad info train in the bud. And to the gentleman in the front who doubted me, thank you. Without your help, I would still be operating with false info in my brain. I wish I had gotten your contact info–email me if you read this 🙂
Other than that, it was a fantastic, wonderful event. This was the world premier of my presentation Up and Running with SSIS; what really made me happy was that several of the attendees approached me afterwards and said that they had really gotten some necessary info out of it.