When your DTS packages get scheduled, a thing to keep in mind is that the SQL Server Agent executes them and they may not work as you intended due to the fact that the Agent is most likely running under a different security context.
Here is a checklist you can use to ensure a smooth transition for packages where the security context changes from the creators context to the Agents context:
* The package is owned by you
* The agent account is a domain account being authenticated by a DC in, say, DOMAIN2
* The SQLAgent is being run under the context of a domain account
* The SQLAgent account and your account are both members of BUILTIN\administrators on the SQL Server
* The SQLAgent account and your domain account are members of the sysadmin fixed server role
* The directory in which the files reside is shared, with
"Change" and "Read" permissions granted to BUILTIN\administrators
* The SQLAgent account and your domain account have been permitted access to the SQL Server database
* These users have not been explicitly DENIED access to any object being "touched" by the DTS package in the database.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.