- SQL Server 2017 Integration Services Cookbook
- Christian Cote Matija Lah Dejan Sarka
- 188字
- 2025-02-25 14:22:28
How to do it...
- We'll first create a folder that will hold the solution files. In our case, we created a folder called C:\Projects\SSISCookbook and we uncompressed the solution file in it, as shown in the following screenshot:

- Now, we open the solution in Visual Studio by double-clicking on the SSISCookBook solution file, as highlighted in the preceding screenshot.
- The solution opens and you will see its projects, as shown in the following screenshot:

The following point will describe the projects that are shown in the Solution Explorer in SQL Server Data Tools (Visual Studio):
- DB.AdventureWorksLT: This is an SQL Server database project that contains the AdventureWorksLT database objects.
- DB.AdventureWorksLTDW: This is the SQL Server database project that contains the staging, DW, the framework database objects. We'll talk about the framework in a subsequent recipe.
- ETL.DW: This is an SSIS project that fills the tables in the DW schema.
- ETL.MasterData: This is an SSIS project that connects to Master Data Services and loads the DW.DimOrderProvenance table in the AdventureWorksDW database.
- ETL.Staging: This is an SSIS project that loads the tables in the staging schema in the AdventureWorksDW database.