Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

Can you administer ssis using the ssis catalog?


Asked by Brennan David on Dec 12, 2021 FAQ



You will administer Integration Services using the SSIS catalog, but your DBA will back up and secure the SSISDB just like any other database. Because of the encryption key specified when creating the catalog, backup and restoring, particularly restoring to a different server, is more involved than a typical database.
Likewise,
The SSIS Catalog is the one place where you will manage SSIS projects and packages, including the configuration and monitoring. If you take a look at SSMS, you will see a new folder, Integration Services Catalogs. The catalog is not set up by default, you will have to create it.
Furthermore, Permissions. The SSISDB catalog uses a DDL trigger, ddl_cleanup_object_permissions, to enforce the integrity of permissions information for SSIS securables. The trigger fires when a database principal, such as a database user, database role, or a database application role, is removed from the SSISDB database.
Keeping this in consideration,
To achieve executing an SSIS package as a different user from SSISDB you need to utilize some functionality from the SQL Server Agent. You need to create a credential that has db_datareader access to SSIS db. You need to setup a Proxy that has rights to Execute Integration Services Packages.
In addition,
The objects that are stored in the SSISDB catalog include projects, packages, parameters, environments, and operational history." The SSISDB catalog stores the packages that you've deployed to the Integration Services server, but before you can deploy the projects to the Integration Services server, the server must contain the SSISDB catalog.