Wednesday, November 26, 2014

Allowing a DBO to manage SSIS packages (SQL 2008)

We have developers that manage their own application's databases (dbo) and SSIS jobs.  In order to give them "least priv" to SQL 2008, this is what I've been doing to give them rights to manage their database(s) and their SSIS jobs on SQL server.

  • Add user admin account to local "Distributed COM Users" group
  • Give "Distributed COM Users" group remote access to the DCOM config for SQL; see http://systems808.blogspot.com/2010/07/access-denied-to-ssis-remotely.html
  • Give user admin account access to msdb database with the following rights:
    • DatabaseMailUserRole
    • db_ssisltduser
    • public (default)
    • SQLAgentOperatorRole
    • SQLAgentReaderRole
    • SQLAgentUserRole
Hope that helps!


For SQL 2012+, see:
https://docs.microsoft.com/en-us/sql/integration-services/service/integration-services-service-ssis-service?view=sql-server-2016

Monday, November 3, 2014

syspolicy_purge_history job failing

Basically, had to fix powershell command line to use the cluster virtual server name for each instance vs the server name...

Reference:
http://support.microsoft.com/kb/955726