Click to edit Master subtitle style05 | Configuration and

Deployment

Richard Currey | Senior Technical Trainer–New Horizons UnitedGeorge Squillace | Senior Technical Trainer–New Horizons Great Lakes

• Troubleshooting

• Debugging

• Logging

• Event Handlers

• Deployment

Module 5 Overview

Topic: Troubleshooting

Topic: Troubleshooting

• Troubleshooting in SSIS

• Troubleshooting approaches

Troubleshooting in SSIS

• The process of determining the source of problems that occur during package execution

• Tasks that can occur during the troubleshooting process–Monitoring execution path–Monitoring values, both data and variable–Monitoring events that occur–Monitoring the outcome of the package

Troubleshooting Approaches

• Debugging– Setting breakpoints– Viewing execution progress– Viewing / modifying variable values– Viewing data flow

• Logging

• Event Handlers

Topic: Debugging

Topic: Debugging

• Breakpoints

• Watches

• Data Viewers

Breakpoints

• Pauses execution when reached

• Enabled for any task or container in the package

• Can be configured to stop at:– Any time-will pause execution every time that the task is

encountered– Hit Count Equals-will pause after a specific number of

times that the breakpoint is reached– Hit Count Greater or Equal-will pause every time after the

threshold value is reached– Hit Count Multiple-will pause when the task is reached a

multiple of the value entered

Watches

• Displays a variable and its associated value during execution

• Values can be modified while execution is paused

• Watch window displays requested variables

• Locals window displays all variables that are currently in scope

Data Viewers

• Data can be copied from the viewer

• Used to watch records flow between data flow transforms

• Can be enabled between any two data flow components– Between a data source and a transform– Between any two transforms– Between transform and data destination

• Will pause the execution of the package while data is examined

DEMODebugging a Package

Topic: Logging

Topic: Logging

• What Is Logging?

• Events

• Log Providers

• Configuring Logging

What Is Logging?

• The process of persisting the details of package execution

• Can be used to determine where package execution failed in a production environment

• Can be used to help troubleshoot performance issues

Events

• Events are the things that happen during package execution

• Events have properties that expose information that can be logged

• Events have some properties that are common to all events and some that are unique for that particular event

• Are the destinations for the messages that are being logged

• Are data destinations so they require connection managers

• Types include text file, Windows Event Log, XML file, SQL Server, and SQL Server Profiler

Log Providers

• Determine the executables to log

• Choose the Log Provider to use

• Determine the events that should be enabled

• Choose the information for each event

Configuring Logging

DEMOConfiguring Logging

Topic: Event Handlers

Topic: Event Handlers

• What Are Event Handlers?

• Configuring Event Handling

• Workflows that only occur when the event occurs

• Are tied to an event and an executable

• Error events are the most commonly defined event handlers

• Control flow is defined for each individual event handler

What Are Event Handlers?

• Choose the executable and event that needs a response

• Design and implement a control flow to execute when the event occurs

Configuring Event Handling

DEMOConfiguring Event Handling

Topic: Deployment

Topic: Deployment

• Deployment Types

• Package Configurations

• Environments

Deployment Types

• Package deployment– The process of moving individual packages to a production

environment

• Project deployment –Moves all packages from a project into the production

environment– Includes all project-level resources

• Deployment can be to SQL Server, file system or SSIS catalog

Package Configurations

• Are only available with package deployment

• Are used to set property values from outside of the package and to persist those values for reuse

• Can be direct or indirect– Direct configurations map an executable and property to a specific

value– Indirect configurations map an executable and a property to the

location where the property value can be found

• Include environment variables, registry entries, XML files, SQL Server, and the parent package variable

DEMOImplementing Configurations

Environments

• Provide similar functionality for packages as configurations– External mapping of property and value

• Multiple environments can be created– Dev– Test– Prod

• Property values can be specified in each environment– Connection string to a different SQL Server instance for

example

• Environment to use can be specified at runtime

DEMOImplementing Environments

©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.