Re: Security Running a DTS Package
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 11 May 2006 10:04:00 -0600
Okay...you need to go back to what I wrote as that will
explain the issues and the differences between when you run
it manually and when you run it as a job.
What do you mean by using sa through the proxy? That's not
quite how it works and I'm not real sure what you mean.
Have the job be owned by a sysadmin. It will then run under
the security context of the service account.
Whatever it is that is causing problems is very likely
related to the service account and the permissions.
What you reported was "when it writes a file the SQL Server
security is no longer valid". If you are writing to
somewhere on the network, the service account needs to be a
domain user with access to the network resource.
Take a look at the following Knowledge Base article for more
info:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On Thu, 11 May 2006 04:07:02 -0700, Chris
<Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello Sue,
Yes I am actually referring to running the package from a job. My problem is
I can run the package manually but when I schedule it the job fails. I am a
member of sysadmin and have even tried using the sa through the proxy on the
job with out success. Job still fails.
-Chris
"Sue Hoegemeier" wrote:
It depends on what you mean by run a package - through a job
or are you executing it manually? If you execute it
manually, it runs under your security context and from your
PC. It sounds like you are referring to executing the
package in a job. In that case, it depends on the job owner.
If the job owner is a sysadmin, then it executes under the
security context of the SQL Agent service account. If the
job is owned by a non-sysadmin, it executes under the
security context of the proxy account.
-Sue
On Tue, 9 May 2006 10:08:02 -0700, Chris
<Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Let's say that the SQL Server is registered using the SA id and pw and the
package owner is the same. There is no SA id in the windows o/s enviroment.
How does it know that SA has rights to write to a drive?
-Chris
"kllyj64" wrote:
The owner of the package has to have write privleges to the drive and folder
you are writing to the file. At the time of the write it is the file
management security that comes into effect.
--
Thanks Kllyj64
"Chris" wrote:
When I run a DTS package and write a file to a drive, what security does the
DTS package use to do this? I know it uses the SQL Server security to run the
package but when it writes a file the SQL Server sceurity is no longer valid?
Can some one help explain this?
Thanks for your help
-Chris
.
- References:
- Re: Security Running a DTS Package
- From: Sue Hoegemeier
- Re: Security Running a DTS Package
- Prev by Date: Import data from Access to SQL2005 on daily basis
- Next by Date: Looping Query not working
- Previous by thread: Re: Security Running a DTS Package
- Next by thread: Re: dynamically set global variables
- Index(es):
Relevant Pages
|
