December 11, 2014 at 6:12 am
Last month I updated an SSIS package to copy a file from one location to another. It failed in both BIDS and when running as a SQL Agent job. I am starting over again this month and want to verify my thinking is correct on security before I go another step forward.
Details: SQL 2008 Enterprise, Visual Studio 2008 Version 9.0.30729.1 SP (but I open BIDS specifically)
Package was created by me. It's stored in TFS. The package creates a file out on a NAS share (A) that both I and the SQL Server Agent account have FULL CONTROL over. The file is then zipped up with Winzip and supposed to be copied to another NAS share (B) that is more restricted. Team A has access to it as well as the DBA team (my team). I have regularly copied, created, and deleted files to and from NAS share B. Usually these files come from NAS share A.
Now, when I run the package from BIDS on my local desktop, I am expecting it to use my permissions for all things. Am I correct or incorrect in this expectation?
When I run it in SQL Server Agent, I expect it to use the SQL Agent Service account regardless of whether the job is scheduled or whether I start it manually. Am I correct or incorrect in this expectation?
December 11, 2014 at 6:39 am
Oh, for heaven's sake. After all this grief with the job and the task, it turns out the problem is the file isn't zipping up properly because a .lst file is missing from my NAS share.
#headdesk
So, not a security issue after all... I'm feeling kinda silly now.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply