Execution Patterns - SQL Server Integration Services Design Patterns - page 57

[MinHI] varchar(50),
[MaxHI] varchar(50),
[AverageHI] varchar(50)
)
This statement modifies the supplied statement by removing the OLEDBDest pre-
fix from the table name and by removing the spaces from the column names. Click the
OK button to create the table and close the Create Table window. Click the Mappings
page and map the available input columns to their matching available destination
columns. Close the OLEDBDest TemperatureStage OLE DB Destination Adapter Edit-
or.
Double-click the data flow path to open its editor. From the General page, copy the
IdentificationString property value. The IdentificationString prop-
erty should be Paths[FFSrc Temperature.Flat File Source Output] .
We will need this value and the value of the PackagePath property of the Data Flow
task (\ Package\DFT Load Temperature Data ) to execute this package with a
data tap.
First, save the SSIS package and deploy it to the catalog. Next, execute the state-
ment in Listing 2-6 to execute the SSIS package with a data tap.
Listing 2-6 . Executing an SSIS Package with a Data Tap
Declare @ExecId bigint
Exec SSISDB.custom.execute_catalog_package_with_Data_tap
@FolderName = 'Chapter2'
,@ProjectName = 'Chapter2'
,@PackageName = 'DataTapTest.dtsx'
,@DataFlowTaskName = '\Package\DFT Load Temperature Data'
,@IdentificationString = 'Paths[FFSrc Temperature.Flat
File Source Output]'
,@DataTapFileName = 'TemperatureRows.csv'
,@ExecutionID = @ExecId Output
,@DataTapMaxRows = 25
Once the package executes (and you can test for rows in the
TestDB.dbo.TemperatureStage table), you should find a CSV file named
TemperatureRows.csv in the < drive >:\Program Files\Microsoft SQL
Server\120\DTS\DataDumps directory, and that file should contain the first 25