SSIS Security Roles -
04-23-2008
, 08:45 AM
Hello....
I am looking to limit what our developers can and cannot do in our SQL 2005
SSIS environment. We no longer have a dedicated DBA and need to share the
process of creating and running packages between our developers and
operations staff(sql admins)....
The three roles that seem to impact SSIS are db_dtsadmin, db_dtsltduser and
db_dtsoperator...each allows for different access to the SSIS environment...
With all of our packages set to be stored in MSDB, I have managed to create
another role and by denying certain stored procs...limit some of what the
developers can do. I basically want the developers to be able to export/view
all packages....I don't want them to execute..I know I can limit this with
rights to the DB...but is there another way to take that Execute Package
right away, even if they are the owner...???
Thanks |