dbTalk Databases Forums  

Package Sercurity Context

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Package Sercurity Context in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
alien2_51
 
Posts: n/a

Default Package Sercurity Context - 03-02-2004 , 10:48 AM






Under what security context does an ActiveX Script task run as if executed
inside the DTS designer...? Where does it get the context, does it
impersonate the user..? I realize that it's different when run as a
scheduled job, whatever credentials the SQL Agent runs under are used... Is
that correct..?

TIA



Reply With Quote
  #2  
Old   
Darren Green
 
Posts: n/a

Default Re: Package Sercurity Context - 03-02-2004 , 12:21 PM






In message <ebqh0YHAEHA.1548 (AT) TK2MSFTNGP12 (DOT) phx.gbl>, alien2_51
<dan.billow@?.o.s.p.a.m.monacocoach.commercialvers ion.invalid> writes
Quote:
Under what security context does an ActiveX Script task run as if executed
inside the DTS designer...? Where does it get the context, does it
impersonate the user..? I realize that it's different when run as a
scheduled job, whatever credentials the SQL Agent runs under are used... Is
that correct..?

TIA


The script and indeed the package is run under the context of the user
executing the package. DTS is client-side, so when using Enterprise
Manager for example it runs on the same machine as EM, under the user
context of logged on user.

If you schedule a package then you basically get the SQL Server Agent
service to call DTSRUN for you, so it is on the same machine as SQL
Server Agent and running under the SQL Server Agent service account. The
caveat to that is for jobs not owned by a sysadmin SQL agent then
impersonates the proxy account, assuming one has been defined.

More info about scheduled packages here-

http://support.microsoft.com/default...b;en-us;269074

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org



Reply With Quote
  #3  
Old   
Darren Green
 
Posts: n/a

Default Re: Package Sercurity Context - 03-02-2004 , 02:39 PM



In message <90F0D812-BAFA-4BA4-80F8-37E1BF2E5305 (AT) microsoft (DOT) com>, KP
<anonymous (AT) discussions (DOT) microsoft.com> writes
Quote:
Is there any way (may be using a script or getting information out of
system tables etc.,) to figure out under what user / service account
one particular package is running? The reason for this question is I
have around 500 packages spread all over my network. Its almost
impossible to find out which account is in use for a specific package
manually.

TIA
KP
You can query sysjobs looking at the owner_sid column. Check syslogins
and the sysadmin column. sysadmins use the SQL Agent account, other
users get the proxy account.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org



Reply With Quote
  #4  
Old   
alien2_51
 
Posts: n/a

Default Re: Package Sercurity Context - 03-02-2004 , 04:39 PM



Thanks Darren...

"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

Quote:
In message <ebqh0YHAEHA.1548 (AT) TK2MSFTNGP12 (DOT) phx.gbl>, alien2_51
dan.billow@?.o.s.p.a.m.monacocoach.c...versi on.invalid> writes
Under what security context does an ActiveX Script task run as if
executed
inside the DTS designer...? Where does it get the context, does it
impersonate the user..? I realize that it's different when run as a
scheduled job, whatever credentials the SQL Agent runs under are used...
Is
that correct..?

TIA


The script and indeed the package is run under the context of the user
executing the package. DTS is client-side, so when using Enterprise
Manager for example it runs on the same machine as EM, under the user
context of logged on user.

If you schedule a package then you basically get the SQL Server Agent
service to call DTSRUN for you, so it is on the same machine as SQL
Server Agent and running under the SQL Server Agent service account. The
caveat to that is for jobs not owned by a sysadmin SQL agent then
impersonates the proxy account, assuming one has been defined.

More info about scheduled packages here-

http://support.microsoft.com/default...b;en-us;269074

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.