In this chapter, we will move to the next object in the Data Services hierarchy of objects used in ETL design: the workflow object. Workflows do not perform any movement of data themselves; their main purpose is to group dataflows, scripts, and other workflows together.
In other words, workflows are container objects grouping pieces of ETL code. They help define the dependencies between various pieces of ETL code in order to provide robust and flexible ETL architecture.
I will also show you how you can query the Data Services repository using database tools in order to query the hierarchy of objects directly and will show you how this hierarchy is stored in repository database tables. This may be very useful if you want to understand a bit more about how the software is functioning "under the hood".
Additionally, we will build a real-life use case ETL code by populating dimension tables in data warehouse. This use case example will include the functionality already reviewed in...