Using Integration Services Roles
SQL Server Integration Services includes the three fixed database-level roles, db_ssisadmin, db_ssisltduser, and db_ssisoperator, for controlling access to packages. Roles can be implemented only on packages that are saved to the msdb database in SQL Server. You assign roles to a package using SQL Server Management Studio. The role assignments are saved to the msdb database.
The following table describes the read and write actions of Windows and fixed database-level roles in Integration Services.
Role |
Read action |
Write action |
|---|---|---|
db_ssisadmin or sysadmin |
Enumerate own packages. Enumerate all packages. View own packages. View all packages. Execute own packages. Execute all packages. Export own packages. Export all packages. Execute all packages in SQL Server Agent. |
Import packages. Delete own packages. Delete all packages. Change own package roles. Change all package roles. .gif "Important note") Important
Members of the db_ssisadmin role and the dc_admin role may be able to elevate their privileges to sysadmin. This elevation of privilege can occur because these roles can modify Integration Services packages and Integration Services packages can be executed by SQL Server using the sysadmin security context of SQL Server Agent. To guard against this elevation of privilege when running maintenance plans, data collection sets, and other Integration Services packages, configure SQL Server Agent jobs that run packages to use a proxy account with limited privileges or only add sysadmin members to the db_ssisadmin and dc_admin roles.
|
db_ssisltduser |
Enumerate own packages. Enumerate all packages. View own packages. Execute own packages. Export own packages. |
Import packages. Delete own packages. Change own package roles. |
db_ssisoperator |
Enumerate all packages. View all packages. Execute all packages. Export all packages. Execute all packages in SQL Server Agent. |
None |
Windows administrators |
View execution details of all running packages. |
Stop all currently running packages. |
The sysssispackages table in msdb contains the packages that are saved to SQL Server. For more information, see sysssispackages (Transact-SQL).
The sysssispackages table includes columns that contain information about the roles that are assigned to packages.
The readerrole column specifies the role that has read access to the package.
The writerrole column specifies the role that has write access to the package.
The ownersid column contains the unique security identifier of the user who created the package. This column defines the owner of the package.
By default, the permissions of the db_ssisadmin and db_ssisoperator fixed database-level roles and the unique security identifier of the user who created the package apply to the reader role for packages, and the permissions of the db_ssisadmin role and the unique security identifier of the user who created the package apply to the writer role. A user must be a member of the db_ssisadmin, db_ssisltduser, or db_ssisoperator role to have read access to the package. A user must be a member of the db_ssisadmin role to have write access.
The fixed database-level roles work in conjunction with user-defined roles. The user-defined roles are the roles that you create in SQL Server Management Studio and then use to assign permissions to packages. To access a package, a user must be a member of the user-defined role and the pertinent Integration Services fixed database-level role. For example, if users are members of the AuditUsers user-defined role that is assigned to a package, they must also be members of db_ssisadmin, db_ssisltduser, or db_ssisoperator role to have read access to the package.
If you do not assign user-defined roles to packages, access to packages is determined by the fixed database-level roles.
If you want to use user-defined roles, you must add them to the msdb database before you can assign them to packages. You can create new database roles in SQL Server Management Studio.
The Integration Services database-level roles grant rights on the Integration Services system tables in the msdb database, but not on the DTS system tables, such as sysdtspackages in the msdb database. You have to grant users rights on the DTS system tables before they can perform certain management tasks, such as importing a DTS package in Management Studio. For more information about DTS support, see Support for Data Transformation Services (DTS) in SQL Server 2008.
Step 1: Open Object Explorer and Connect to Integration Services
Before you can assign roles to packages by using SQL Server Management Studio, you must open Object Explorer in SQL Server Management Studio and connect to Integration Services.
The Integration Services service must be started before you can connect to Integration Services.
To open Object Explorer and connect to Integration Services
Open SQL Server Management Studio.
Click Object Explorer on the View menu.
On the Object Explorer toolbar, click Connect, and then click Integration Services.
In the Connect to Server dialog box, provide a server name. You can use a period (.), (local), or localhost to indicate the local server.
Click Connect.
Step 2: Assign Reader and Writer Roles to Packages
You can assign a reader and a writer role to each package.
Assign a reader and writer role to a package
In Object Explorer, locate the Integration Services connection.
Expand the Stored Packages folder, and then expand the subfolder that contains the package to which you want to assign roles.
Right-click the package to which you want to assign roles.
In the Packages Roles dialog box, select a reader role in the Reader Role list and a writer role in the Writer Role list.
Click OK.
Create a User-Defined Role
SQL Server (the MSSQLSERVER service) must be started before you can connect to the Database Engine and access the msdb database.
To create a user-defined role
Open SQL Server Management Studio.
Click Object Explorer on the View menu.
On the Object Explorer toolbar, click Connect, and then click Database Engine.
In the Connect to Server dialog box, provide a server name and select an authentication mode. You can use a period (.), (local), or localhost to indicate the local server.
Click Connect.
Expand Databases, System Databases, msdb, Security, and Roles.
In the Roles node, right-click Database Roles, and click New Database Role.
On the General page, provide a name and optionally, specify an owner and owned schemas and add role members.
Optionally, click Permissions and configure object permissions.
Optionally, click Extended Properties and configure any extended properties.
Click OK.
|
.gif "Integration Services icon (small)")
Stay Up to Date with Integration Services