1190
Part IX: Business Intelligence
names or fi lenames. To share a confi guration in a subsequent package, choose the same
confi guration type, and then specify the same storage location (for example, XML fi lename)
as the initial package. When prompted by a dialog warning that the confi guration already
exists, select Reuse Existing.Converting to the Project Model from the Package (Legacy) Model
Pre-SQL Server 2012 SSIS solutions often involved Parent Child Packages, which were
deployed using Confi gurations and Parent Package Variables. To allow these solutions to
take advantage of the new Project Model, there is a Project Conversion Wizard available to
step through a conversion to the Project model. This wizard accepts a Project as input and
converts all execute package tasks to use Project References, and all confi gurations to use
Project or Package level Parameters. Note that after a project converts, it can no longer use
Confi gurations.Using the Project Deployment Model
SSIS developers have often created projects containing related packages. But at deployment
time, the packages and their connection managers were atomic. Preserving any dependen-
cies between packages at deployment had to be done manually. The new Project Deployment
Model attempts to remedy this by treating an entire Project and all its Packages,
Parameters, and connection managers as one unit throughout development, deployment,
and executions.Using the Build button in SSIS now actually compiles a new fi le, which has the exten-
sion .ispac. Create an .ispac fi le by clicking Project ➪ Build. An .ispac fi le is created,
which is saved to the bin folder under your project. (You can change this location by
going to project ➪ Project Properties ➪ Confi gurationProperties ➪ Build on the Right
Outputs ➪ outputpath.)Using the Project Deployment Model, SSIS Projects can be deployed only to SQL Servers,
specifi cally to the new SSIS catalog, called SSISDB. (Packages using the package deploy-
ment model can still be deployed to the MSDB system database.)To successfully start and use the SSIS catalog, you must enable CLR on the SQL Server. You can do this via a prompt
that appears while confi guring the catalog, or you can enable it by executing:
sp_configure 'clr enabled', 1;
GO
RECONFIGURE
GO
For more information on confi guring the SSIS catalog for initial use, see “Create the SSISDB Catalog” at http://
msdn.microsoft.com/en-us/library/gg471509(v=sql.110).aspx.c52.indd 1190c52.indd 1190 7/31/2012 10:29:31 AM7/31/2012 10:29:31 AM
http://www.it-ebooks.info