Datasheet

Chapter 1: SSIS Solution Architecture
28
In this case, the impact on both the source and destination machines is reduced because the SSIS server
would handle the data flow transformation logic. This architecture also provides a viable SSIS
application server approach, where the machine can handle all the SSIS processing packages no matter
where the data is coming from and going to.
The drawbacks to this approach lie in the capability to optimize the source extraction and destination
import, increased network I/O (because the data has to travel over the wire two times), as well as
licensing.
Design Review
As you can see, you have a lot to juggle at once when you are planning and building an ETL or data -
integration solution. In many cases (such as the infrastructure), all you need to do is set the ball in
motion with your IT hardware group. If you are working with a smaller team, you will have more to do,
but the discussion in this “ Design ” section gives you direction to go in, and helps you stay on top of
your project. Sometimes you may feel like you are juggling several balls at once, but you ’ ll be better off
starting early, rather than trying to juggle ten balls in the middle of the project!
Solution
Now it is time to focus on the SSIS ETL solution. The project is in motion, expectations are set with the
stakeholders, and you have laid the foundation to a successful project.
The next step is about designing and implementing your SSIS solution. Just when you think that you have
a handle on things, you now have to dive into the details of data and processes! This section launches you
into your SSIS design . . .not by providing all the steps in these next few pages, but by giving you the
driving directions on where to find your design and solution answers in the rest of this book.
Figure 1-13
Execution Location
Source Data Path
Destination Data Path
Source files/data
Extraction Impact
Execution
Impact
Destination files/data
Load Impact
c01.indd 28c01.indd 28 9/24/09 11:26:43 AM9/24/09 11:26:43 AM