Wiley Expert SQL Server 2005 Integration Services 978-0-470-13411-5 User Manual
Product codes
978-0-470-13411-5
until SSIS enumerates to the end of the collection. Out of the box, you can enumerate through a collec-
tion of files in a directory, records in a table, or a list of items that you type. There are other types of enu-
merators that you can specify, and you can even write your own enumerator.
tion of files in a directory, records in a table, or a list of items that you type. There are other types of enu-
merators that you can specify, and you can even write your own enumerator.
It’s also important to note that after you place a set of tasks inside a container, they can only relate
through precedence constraints to other tasks in the container. An individual task inside the container
can never relate directly to anything else outside the container. The last thing to point out about contain-
ers is that you can embed containers inside containers.
through precedence constraints to other tasks in the container. An individual task inside the container
can never relate directly to anything else outside the container. The last thing to point out about contain-
ers is that you can embed containers inside containers.
Review Conclusion
Even though this walk-through only highlights the data flow and control flow, you still can see that SSIS
is a broad-featured tool capable of a lot of diverse applications.
is a broad-featured tool capable of a lot of diverse applications.
In the end, it’s all about the data — ensuring that the information is handled in the right way to meet
your needs. This does not minimize the supporting requirements such as transactions handling, deploy-
ment, and execution monitoring, because these are important pieces to building a stable SSIS environ-
ment. When you take the primary data processing tasks and add in administration, error handling,
scalability, testing, and deployment, the result is like juggling spinning plates. It’s no wonder why ETL
consumes up to 70 percent of an enterprise data warehouse development effort.
your needs. This does not minimize the supporting requirements such as transactions handling, deploy-
ment, and execution monitoring, because these are important pieces to building a stable SSIS environ-
ment. When you take the primary data processing tasks and add in administration, error handling,
scalability, testing, and deployment, the result is like juggling spinning plates. It’s no wonder why ETL
consumes up to 70 percent of an enterprise data warehouse development effort.
You may know this already: If you can reduce the amount of time it takes to build an ETL solution
(including the supporting architecture), then your projects are in a better position for success. This is the
value proposition of SSIS — a tool that can integrate all the needed features for a complete ETL system in
an architecture that is supportable and extendable. With the right tool and right architecture, more time
can be spent on testing the data and presenting the data to the users.
(including the supporting architecture), then your projects are in a better position for success. This is the
value proposition of SSIS — a tool that can integrate all the needed features for a complete ETL system in
an architecture that is supportable and extendable. With the right tool and right architecture, more time
can be spent on testing the data and presenting the data to the users.
Summar y
There are two keys to a successful ETL solution:
❑
Using the right enterprise ETL tool
❑
Employing the right ETL architecture to meet the requirements
First, with SSIS, you’ll find the out-of-the-box features provide the depth and breadth of functionality
and flexibility needed to create efficient, reliable, and scalable solutions. What’s more, the usability and
rapid learning curve reduce solution development time. The second ingredient is addressed in the rest of
the pages of this book. As a practical guide for SSIS ETL development, you will learn ways to implement
your ETL solution requirements from the data to the administration and everything in-between. Putting
it all together to get a solution over the goal line requires knowing the big picture and coordinating all
the pieces.
and flexibility needed to create efficient, reliable, and scalable solutions. What’s more, the usability and
rapid learning curve reduce solution development time. The second ingredient is addressed in the rest of
the pages of this book. As a practical guide for SSIS ETL development, you will learn ways to implement
your ETL solution requirements from the data to the administration and everything in-between. Putting
it all together to get a solution over the goal line requires knowing the big picture and coordinating all
the pieces.
Now that we have made the case for SSIS and reviewed some main features, it is time to dig in. In
Chapter 2, we will start by considering scripting. Using the Script Task and Script Component in the
right ways is central to applying SSIS, and in many of the later chapters, some scripting will be used to
handle common situations that cannot be easily applied with other out-of-the-box features.
Chapter 2, we will start by considering scripting. Using the Script Task and Script Component in the
right ways is central to applying SSIS, and in many of the later chapters, some scripting will be used to
handle common situations that cannot be easily applied with other out-of-the-box features.
20
Chapter 1: Getting Started
04_134115 ch01.qxp 4/24/07 6:40 PM Page 20