Situation:
I have a group of SSIS administrators who should be able to:
The requirement states that All ETL administrators must have full privileges to administer and monitor the SSIS catalog, and to import and manage projects.
I'm not sure if the new "SSIS Admin" is the best solution for my problem.
Problem:
I created a sql server login and mapped the SSISAdmin group (windows server) to the sql server login (convenient I called it also SSISAdmin).
I mapped the SSISAdmin sql server login to the SSISDB Catalog database.
Now I'm considering whether the SSIS_Admin of the SSISDB database will suffice or should I consider taking the db_owner role? I'm not sure or don't find a clear answer on the permission differences between the two database level roles, except that they both state that the roles allow the user to do "anything & everything" on the database. The first thing that comes to mind is that I don't want the SSISAdmins to be able to delete the entire SSISDB database (db_owner)! Will the SSIS_Admin role prevent this... What are the most profound differences between the two and why did Microsoft introduce this role specifically on the SSIS Catalog.
Thank you