New management role for SSIS 2016

SSIS 2016 management

Working in regulated environments presented some challenges with the SQL Server Integration Services, SSIS, project deployment model which was introduced with the 2012 release of SQL Server. Specifically, there was no way to use the native reporting and dashboard features of the Integration Services Catalog without being a system administrator or having the ability to administer the SSISDB catalog. That's a clear violation of the separation/segregation of duties polices for the major compliance regulations.

The upcoming release of SQL Server 2016 provides a new built-in role, ssis_logreader that should address the need to allow support staff the ability to support SSIS without violating separation of duties requirement. They will be able to view the history for a package - its average, minimum and maximum durations along with run frequencies as well as delve into any errors associated to those runs. All of this from the comfort of the native reports built within the SQL Server Management Studio. No more will they need to write custom queries and master the object model.

We see this as an excellent step forward in the maturation of the administrative experience for SSIS.