Re: Security Running a DTS Package
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Wed, 10 May 2006 21:09:16 -0600
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
.
- Prev by Date: Re: "Execution was canceled by user." bug when calling DTS from .NET
- Next by Date: Re: SSIS Transfer SQL Server Objects Task - Probs
- Previous by thread: SSIS Script Transformation - dunno how to return a null
- Next by thread: Re: Security Running a DTS Package
- Index(es):
Relevant Pages
|