jodebrui and perrysk-msft Wwi update (#255)
Awesome update!
Latest commit 58bd2e8 Jun 28, 2017
Permalink
..
Failed to load latest commit information.
wwi-ssis Wwi update (#255) Jun 28, 2017
README.md Wwi update (#255) Jun 28, 2017
wwi-ssis.sln Wwi update (#255) Jun 28, 2017

README.md

ETL Process for WideWorldImporters

This SSIS project performs ETL from the transactional database WideWorldImporters into the OLAP database WideWorldImportersDW for long-term storage and analytics.

Contents

About this sample
Before you begin
Running the sample
Sample details
Disclaimers
Related links

About this sample

  1. Applies to: SQL Server 2016 (or higher)
  2. Key features: Core database features
  3. Workload: ETL
  4. Programming Language:
  5. Authors: Greg Low, Denzil Ribeiro, Jos de Bruijn
  6. Update history: 25 May 2016 - initial revision

Before you begin

To run this sample, you need the following prerequisites.

Software prerequisites:

  1. The databases WideWorldImporters and WideWorldImportersDW running on SQL Server 2016 (or higher) or Azure SQL Database. These can be on different servers.
  2. Visual Studio 2015 Update 3 (or higher). At the time of writing, Visual Studio 2017 does not yet support Integration Services projects. You will need to install Visual Studio 2015 to open the SSIS project.
  3. SQL Server 2016 (or higher) Integration Services.
    1. This needs to be installed on the same machine as Visual Studio to be able to build the project.
    2. Make sure you have already created an SSIS Catalog. If not, to do that, right click Integration Services in Object Explorer, and choose to add catalog. Follow the defaults. It will ask you to enable sqlclr and provide a password.

Running the sample

  1. Open the solution file wwi-ssis.sln in Visual Studio.

  2. Build the solution. This will create an SSIS package Daily ETL.ispac under Daily ETL\bin\Development.

  3. Deploy the SSIS package.

    1. Open the "Daily ETL.ispac" package from Windows Explorer. This will launch the Integration Services Deployment Wizard.
    2. Under "Select Source" follow the default Project Deployment, with the path pointing to the "Daily ETL.ispac" package.
    3. Under "Select Destination" enter the name of the server that hosts the SSIS catalog.
    4. Select a path under the SSIS catalog, for example under a new folder "WideWorldImporters".
    5. Finalize the wizard by clicking Deploy.
  4. Create a SQL Server Agent job for the ETL process.

    1. In SSMS, right-click "SQL Server Agent" and select New->Job.
    2. Pick a name, for example "WideWorldImporters ETL".
    3. Add a Job Step of type "SQL Server Integration Services Package".
      • Select the server with the SSIS catalog, and select the "Daily ETL" package.
      • Under Configuration->Connection Managers ensure the connections to the source and target are configured correctly. The default is to connect to the local instance.
    4. Click OK to create the Job.
  5. Execute or schedule the Job.

Sample details

The ETL package Daily ETL.ispac is used to migrate data from the WideWorldImporters database to the WideWorldImportersDW database as the data changes. The package is run periodically (most commonly daily).

The design of the package uses SSIS to orchestrate bulk T-SQL operations (rather than as separate transformations within SSIS) to ensure high performance.

Dimensions are loaded first, followed by Fact tables. The package can be re-run at any time after a failure.

The workflow is as follows:

Alt text

It starts with an expression task that works out the appropriate cutoff time. This time is the current time less a few seconds. (This is more robust than requesting data right to the current time). It then truncates any milliseconds from the time.

The main processing starts by populating the Date dimension table. It ensures that all dates for the current year have been populated in the table.

After this, a series of data flow tasks loads each dimension, then each fact.

Disclaimers

The code included in this sample is not intended to be used for production purposes.

Related Links

For more information, see these articles: