In my experience, Data Source Views are not commonly used in SSIS packages. I can imagine a use for them. If I were the ETL architect leading a large team of developers on a data warehouse project, I might use the DSV to simplify the development efforts of members of my team. Using AdventureWorks as an example, I may have one team working on a star schema based around FactInternetSales and another team working on a star schema based around FactResellerSales. As I create my package templates for the team to use I can include the DSV to simplify their view of an otherwise complex dimensional model.
The MSDN article, Using Data Source Views in Packages lists the advantages of using DSVs in packages as follows:
A data source view can be defined one time and then used by multiple data flow components.
A data source view can be refreshed to reflect changes in its underlying data sources.
A data source view caches the metadata from the data sources on which it is built.
A data source view can focus the lists of objects that appear in the user interface of data flow components.
It is important to note that there are not any dependencies between a DSV and the packages that reference it. When a package uses a DSV, the definition of the view is added to package source code in the data flow component that uses it. If you delete all of the DSVs from an existing solution, all of the packages that used those DSVs will continue to function.
So here is how you use a DSV in an Integration Services package:
I hope this post will help someone. If you have any questions please add a comment below.