catalog.deny_permission (SSISDB Database)
Denies a permission on a securable object in the Integration Services catalog.
This stored procedure allows you to deny the permission types described in the following table:
|
permission_type Value |
Permission Name |
Permission Description |
Applicable Object Types |
|---|---|---|---|
|
1 |
READ |
Allows the principal to read information that is considered part of the object, such as properties. It does not allow the principal to enumerate or read the contents of other objects contained within the object. |
Folder, Project, Environment, Operation |
|
2 |
MODIFY |
Allows the principal to modify information that is considered part of the object, such as properties. It does not allow the principal to modify other objects contained within the object. |
Folder, Project, Environment, Operation |
|
3 |
EXECUTE |
Allows the principal to execute all packages in the project. |
Project |
|
4 |
MANAGE_PERMISSIONS |
Allows the principal to assign permissions to the objects. |
Folder, Project, Environment, Operation |
|
100 |
CREATE_OBJECTS |
Allows the principal to create objects in the folder. |
Folder |
|
101 |
READ_OBJECTS |
Allows the principal to read all objects in the folder. |
Folder |
|
102 |
MODIFY_OBJECTS |
Allows the principal to modify all objects in the folder. |
Folder |
|
103 |
EXECUTE_OBJECTS |
Allows the principal to execute all packages from all projects in the folder. |
Folder |
|
104 |
MANAGE_OBJECT_PERMISSIONS |
Allows the principal to manage permissions on all objects in the folder. |
Folder |
The following list describes some conditions that may raise an error or warning:
-
If permission_type is specified, the procedure denies the specified permission that is explicitly assigned to the specified principal for the specified object. Even if there are no such instances, the procedure still returns a success code value (0).
-
If permission_type is omitted, the procedure denies all permissions for the specified principal to the specified object.
