Some work arounds were shown for configuring the Source and Destination
database items in the editor, as some of the default actions of this editor are error
prone. The article did not discuss how well the database was transferred, though
it was shown that the entire user created Tables, Stored Procedures, and Views
were copied.
On Using Event
Handlers in SSIS
Executables such as packages, for loop, task host containers, etc., raise events at run
time. The most common event is a task that may fail. This raises an OnError event,
the default event, when the task fails. These events can be leveraged by handling the
event in such a way that some other task can be accomplished or information about
the failure gleaned. Thus, by using event handlers the package's functionality
is extended.
In this exercise, you will create a package that is sure to fail! When this happens you
notify by email that the task did fail using an event handler for the OnError event.
You will also learn about the OnPostExecute event to ping your default gateway to
verify that the mail can go out of your machine. Albeit a contrived example, you will
also learn about the Execute Package Task and the Execute Process Task.
The SSIS designer comes with a number of standard event handlers, as shown in the
following screenshot.
Using an Event Handler in SSIS
[ 240 ]
Hands-On Exercise: Creating a Project
with Two Packages
In order to follow the steps as indicated, you will need to create a Business
Intelligence project that has two packages.
Pages:
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171