Loading a PDW Region in APS - SQL Server Integration Services Design Patterns - page 255

Return to the Control Flow tab and copy the SalesMart 2013 data flow again. Re-
name it Sales Mart 2015 . Using the code in Listing 8-9 , replace the SQL command in
the OLE DB Source.

Listing 8-9 . SQL Command for 2015 Data

/* Retrieve sales for 2015 */
SELECT

orderID
, orderDate
, customerID
, webID
FROM PDW_Example .dbo.FactSales
WHERE orderDate >= '2015-01-01'
AND orderDate < '2016-01-01';

You are now ready to execute the package! Press F5 or navigate to Debug Start

Debugging. Your package should execute, and you should see a successful result.

Limitations

ETL developers and data integration engineers should be aware of the following limita-
tions and behaviors in PDW when developing ETL solutions:

• PDW is limited to a maximum of ten (10) active, concurrent loads. This
number applies to the appliance as a whole, regardless of the number of
Compute nodes, and cannot be changed.
• Each PDW destination adapter defined in an Integration Services pack-
age counts as one concurrent load. An Integration Services package with
more than ten PDW destination adapters defined will not execute.
• As previously mentioned, not all SQL Server data types are supported in
PDW. Refer to the list in Table 8-1 under “ETL vs. ELT,” or in your
PDW documentation, for more details.

A small amount of overhead is associated with each load operation. This overhead
is a necessary part of operating in a distributed environment. For example, the loading