When you run the package manually, it executes under your
security context and from your PC. When you schedule it as a
job, it runs from the server and under the security context
of the service account for SQL Agent (usually...depends on
job owner and some other things). But that's the differences
that generally lead to people having problems with packages
that run manually but fail when scheduled. You can find more
info in the following article:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?kbid=269074
-Sue
On Tue, 17 May 2005 10:23:05 -0700, "Dave"
<Dave (AT) discussions (DOT) microsoft.com> wrote:
Quote:
I created a package on our dev server and can manually execute it OK from
Enterprise Manager, but when I schedule it, the job fails.
I'm having difficulty determining why this happens or where the error should
appear. Are there common things I can check for, or settings I need to have
in order for the job run?
Thanks, Dave. |