SQL Server 2012 Integration Services introduces a new approach for deploying SSIS projects, known as Project Deployment Model.
The project deployment model allows each SSIS project to be treated as a single unit, to be configured and deployed as a whole. A project can contain one or more packages, one or more parameters, and one or more connection managers.Under the project deployment model all of these are deployed to the destination SSIS server as a single unit.
Deployed SSIS projects are stored in the SSISDB catalog.The SSISDB catalog is used to store SSIS project and package definitions, as well as other SSIS metadata.
The key features of this new deployment model are the Integration Services catalog, environments, and parameters. The new deployment model is designed to make deployment and administration of SSIS packages and ETL systems easier across multiple environments.
In SQL Server 2005, 2008 you would deploy packages into SQL Server’s msdb database or to the filesystem. Now, in SQL Server 2012’s project deployment model, you deploy to the SSIS catalog.
An SSIS package created in an earlier version of SQL Server cannot be deployed directly to the SSIS server; it first needs to be converted by the SQL Server Integration Services Project Conversion Wizard to compile it into a deployment file, which can then be deployed to the SSISDB catalog.
Setting the SSIS Catalog
When you first install Integration Services, the SSIS catalog will need to be created. Create it manually by right-clicking on the Integration Services folder in the Database Engine in SSMS and selecting Create Catalog.
A create catalog wizard, guides you through the process of creating the catalog.you must also have the Common Language Runtime (CLR) integration turned on by checking the Enable CLR box.The default name of the database is SSISDB and cannot be renamed.The Create Catalog prompt will ask for a password. This password creates a database master key, and the master key encrypts sensitive data in the catalog.Click OK to create the database and catalog.
The project deployment model allows each SSIS project to be treated as a single unit, to be configured and deployed as a whole. A project can contain one or more packages, one or more parameters, and one or more connection managers.Under the project deployment model all of these are deployed to the destination SSIS server as a single unit.
Deployed SSIS projects are stored in the SSISDB catalog.The SSISDB catalog is used to store SSIS project and package definitions, as well as other SSIS metadata.
The key features of this new deployment model are the Integration Services catalog, environments, and parameters. The new deployment model is designed to make deployment and administration of SSIS packages and ETL systems easier across multiple environments.
In SQL Server 2005, 2008 you would deploy packages into SQL Server’s msdb database or to the filesystem. Now, in SQL Server 2012’s project deployment model, you deploy to the SSIS catalog.
An SSIS package created in an earlier version of SQL Server cannot be deployed directly to the SSIS server; it first needs to be converted by the SQL Server Integration Services Project Conversion Wizard to compile it into a deployment file, which can then be deployed to the SSISDB catalog.
Setting the SSIS Catalog
When you first install Integration Services, the SSIS catalog will need to be created. Create it manually by right-clicking on the Integration Services folder in the Database Engine in SSMS and selecting Create Catalog.
A create catalog wizard, guides you through the process of creating the catalog.you must also have the Common Language Runtime (CLR) integration turned on by checking the Enable CLR box.The default name of the database is SSISDB and cannot be renamed.The Create Catalog prompt will ask for a password. This password creates a database master key, and the master key encrypts sensitive data in the catalog.Click OK to create the database and catalog.
- Enable CLR Integration - Checked
- Enable Automatic Execution Of Integration Services Stored Procedure At SQL Server Startup - Unchecked
- Name Of The Catalog Database - SSISDB
- Password - Provide your password.
No comments:
Post a Comment