Database Reference
In-Depth Information
you don't need to prepare anything in the package to utilize it. Let's jump right into
how to set up the logging and design patterns to report on that data.
Setting Up Catalog Logging
As I mentioned earlier, the benefit of catalog logging is that you don't need to modify
the package at all to use the logging output. The only preparation you need to do is to
make sure your package is set to the project deployment type and deploy the package
to the SSIS Catalog.
To begin setting up catalog logging and reporting, you will create an SSIS Catalog.
You can do this by connecting to the database instance. If Integration Services is in-
stalled, you will see a node entitled Integration Services Catalogs. If you create a new
catalog named SSISDB , it will look like Figure 15-3 .
Figure 15-3 . The SSISDB catalog
At this point, you are ready to deploy your package. First, though, you should make
sure the project is set to use the project deployment model. You can do this by right-
clicking on the project. If you see the option for Convert to Package Deployment
Model, as shown in Figure 15-4 , you are in this mode.
 
 
 
Search WWH ::




Custom Search