1188
Part IX: Business Intelligence
package design surface; and choose Logging. On the Providers and Logs tab, add a provider
for each output type that will be logged (multiple are allowed). On the Details tab, specify
the events for which log entries will be written; the advanced view, also enables selecting
which columns will be included in each event’s log entry.The tree view in the left pane represents the container hierarchy of the package. The check
boxes correspond to each object’s LoggingMode property: clear for Disabled, a black check
for Enabled, and a gray check for UseParentSetting (logging settings inherited from the
parent). By default, all objects inherit from the package settings. Highlighting an item in
the tree displays the details for that object in the current tab. Providers can be confi gured
only for the package, and any object with UseParentSetting will have its options grayed
out in deference to its parents’ settings.The standard log providers are as follows:■ (^) Text File: Writes a comma-separated-value text fi le. Confi gure with an appropriate
File connection manager.
■ (^) SQL Profi ler: Writes a .TRC fi le that can be viewed in the Profi ler application.
■ SQL Server: Writes log entries to the dbo.sysssislog table in the database indi-
cated by the associated OLE DB connection manager. Any database can be chosen to
host this table. If the table does not exist, then it will be created on fi rst use.
■ (^) Event Log: Writes log entries to the Windows application event log on the computer
that executes the package. No confi guration is required.
■ (^) XML File: Writes an .XML fi le. Confi gure with an appropriate File connection
manager.
After you construct a useful set of event/column combinations, save it as a template and
reload on other packages.
Deploying and Executing Projects and Packages
Once a package is developed and working properly, it must be deployed to a server where
it can be executed to perform its designated tasks. In this section the new Project
Deployment Model is explained, as well as the Package Deployment Model (sometimes
referred to as Legacy or File deployment).Using the Package Deployment Model
Package Confi gurations used to be the only way to enable developers to quickly deploy
packages between servers and environments, providing a way to set properties within the
package based on environment-specifi c confi gurations. Although effective, the learning
curve for this method of confi guring packages proved to be one of the most challeng-
ing features to learn. There are, however, countless multipackage solutions deployed toc52.indd 1188c52.indd 1188 7/31/2012 10:29:31 AM7/31/2012 10:29:31 AM
http://www.it-ebooks.info