dbTalk Databases Forums  

Package execution by a end-user

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


Discuss Package execution by a end-user in the microsoft.public.sqlserver.dts forum.



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

Default Package execution by a end-user - 05-24-2004 , 05:05 PM






Hi,
Is it possible to setup a DTS Package and authorizations
such that a end-user can Execute the package but can't
change the design/settings of it, and if so what
authorizations (SQL/Windows) need to be setup for this?

(The package will be created and tested by a Developer but
once it is done, the production process needs to be
manually triggered and monitored by someone and it can't
be automated at this time).

Would appreciate any inputs. Thanks in advance.


Reply With Quote
  #2  
Old   
Ashish Ruparel [MSFT]
 
Posts: n/a

Default RE: Package execution by a end-user - 05-24-2004 , 10:51 PM






Hi Basky,

While saving the DTS Package, you get options to enter
1. Owner Password
2. User Password.

1. Owner Password - whenever a user tries to enter into the design mode of
the DTS Package, he will be prompted for the password. Without which the
user will not be able to view or change the design of the Package.

2. User Password - Whenever the use tries to execute the dts package,
(except from the design mode) will be prompted for the user password.
Without which the user will not be able to execute the package.

You can leave either or both of the password as blank.

In you case you can enter an owner password, so the users in the production
environment will not be able to enter the design mode of the package.
Though, they will be able to execute the package.


HTH

Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.


Reply With Quote
  #3  
Old   
Basky Alur
 
Posts: n/a

Default RE: Package execution by a end-user - 05-25-2004 , 12:01 PM



Ashish,
This definitely helps, and thanks a lot, first of all. What roles/permissions must the end-user be given in SQL to accomplish this - that they are able to execute some packages but not alter anything.

Also, Is it possible to assign these 'authorizations' (as to who can design, who can execute etc.,) to a higher-level object, say userIDs or Roles and use integrated security, rather than providing passwords at the individual package-level? I'm trying to see if maintenance could be reduced as well as risks associated with forgotten passwords etc.

Thanks again,
Basky.

Reply With Quote
  #4  
Old   
Ashish Ruparel [MSFT]
 
Posts: n/a

Default RE: Package execution by a end-user - 05-25-2004 , 05:03 PM



Hi Basky,

Currently the only method of securing the packages would be assigning
passwords to the individual packages.


Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.


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.