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

@ExecutionID
,@object_type = @ObjectType
,@parameter_name = N'LOGGING_LEVEL'
,@parameter_value = @logging_level

/* Call the catalog.start_execution (self-explanatory)

*/

Exec catalog.start_execution
@ExecutionID

end

Testing the Data Tap Procedure

Before we begin this exercise, please visit http://andyweather.com/data/
WeatherData_Dec08.zip to obtain some real-world temperature and humidity
weather data collected at my weather station in Farmville, Virginia. The compressed
file ( WeatherData_Dec08.zip ) contains a single CSV file named
sensor1-all.csv . The file is two folders down, located at
Dec08\TH\sensor1-all.csv . Unzip the compressed file and store it in your file
system. I prefer to store data related to test projects inside a folder named Data in the
SSIS solution directory. It doesn't matter where you store the file as long as you re-
member where you put it.
Add a new SSIS package to the Chapter2 project and rename it
DataTapTest.dtsx . Drag a Data Flow task onto the control flow and rename it
DFT Load Temperature Data . Open the Data Flow Editor (tab) and drag a Flat File
source adapter onto the design surface. Rename the Flat File source adapter FFSrc
Temperature . Open the Flat File Source Adapter Editor and click the New button to
the right of the Flat File Connection Manager drop-down. Clicking the New button
does a couple things for you:

1. It creates a new Flat File connection manager.

2. It opens the new Flat File Connection Manager Editor.

Set the name of the Flat File connection manager to FFCM Temperature . Click
the Browse button and navigate to the folder containing the sensor1-all.csv file
(remember to change the extension filter in the Open dialog from *.txt to * .csv .