July 24, 2013 at 11:05 am
I have a ssis package given by a developer that imports data from an oracle database to SQL server.
I setup a job running on this SQL server to run this package, it hangs, running forever.
But if I run this package separately on visual studio on the server, it is fine, if using the DTExec tool it runs fine too.
I use SQL server agent service account to run this package that stored in the file system.
The SQL agent account is a domain account.
I wonder why it failed, the strange thing is if I create a proxy account that uses the same domain account SQL agent service use, and run the package using the proxy account, it will work, why is that?
They are actually the same domain account.
July 24, 2013 at 1:05 pm
If you use the service account directly (so without a proxy), there are still some very minor differences in permissions. I've read about it a long time ago and don't remember the details, but I could be related to some "sandboxing" of agent in SQL Server. I don't know 🙂
Anyway, the moral of the story is: don't use the service account directly 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 24, 2013 at 1:19 pm
update:
Here is what I found out, after I need to restart SQl agent serivce, for I just installed oracle client on the server, and the SQl agent account does not pick up the oracle path, I did a restart, then run by sql agent service , then it works!
But now sure why proxy account that uses the same domain account works before I restart.
Thanks,
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply