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

Note Actually, selecting Step Into or Step Over from the Debug drop-down menu
also starts the BIDS debugger.
• In Solution Explorer, right-click the package and select Execute Pack-
age from the menu.
• When the package has completed execution in Debug mode, restart the
package in one of these ways:
• By holding Ctrl+Shift and pressing the F5 key
• Using the VCR Restart button on the toolbar
• Clicking the Debug drop-down menu and clicking Restart
Here are some ways to stop the debugger once the package execution completes (or
whenever a Debug mode Stop is desired):
• Hold Shift and press the F5 key.
• Click the VCR Stop button (the square) on the toolbar.
• Click the Debug drop-down menu and select Stop Debugging.
• Click the Debug drop-down menu and select Terminate All.
• Click the Package Execution Completed link beneath the Connection
Managers tab.
Command-Line Execution
Command-line SSIS package execution uses the DTEXEC utility ( DtExec.exe ).
DTEXEC supports project and package deployment models. You can manually invoke
DTEXEC from inside BIDS by clicking the Debug drop-down menu and selecting
Start Without Debugging (or by holding the Ctrl key and pressing F5). You can also
manually start DTEXEC from a command prompt.
DTEXEC isn't often invoked manually. Instead it's common to see DTEXEC com-
mand lines used with scheduling software to execute SSIS packages in production en-
vironments. For example, when you schedule an SSIS package using SQL Server
Agent (covered later in this chapter), DTEXEC is instantiated.