April 28, 2008 at 8:20 am
Any suggesions/best practices on giving a user privelege to view and update DTS Packages only?
¤ §unshine ¤
¤ §unshine ¤
April 28, 2008 at 9:13 am
Yep, install personal edition on thier machine. send them a copy, let them change it, send it back, you deploy.
Seriously, people shouldn't update production packages on the server, it's like updating production code somewhere. Let them change it in a separate environment and then you, or someone else, can test and deploy it.
April 28, 2008 at 9:25 am
We allow developers to create and run packages in a dev environment but only DBAs can move it to and schedule it in production.
Greg
April 28, 2008 at 9:27 am
We are trying to implement a rotational DTS Support for production. So I'm not sure the personal install and migration in one day would work, it would still involve a minimum of 2 people.
¤ §unshine ¤
May 2, 2008 at 10:40 am
Add a role e.g. DTS_Developer to msdb, grant the following permissions to the role:
sp_add_dtspackage EXECUTE
sp_enum_dtspackages EXECUTE
sp_get_dtspackage EXECUTE
sp_get_dtsversion EXECUTE
Add the users to the role.
Greg
May 2, 2008 at 11:14 am
Greg's idea will work, though I'd still be way of support people being able to change packages. At the very least, they should edit the package in a dev server, not live as they could cause more problems.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply