Database Reference
In-Depth Information
is the file system and configures the package path text box with the full path of the dtsx
file I double-clicked. Neat.
If I execute Package2.dtsx using the Execute Package Utility, the Package Ex-
ecution Progress form displays, informing me of the package's execution progress
(how appropriate) and the message box appears as it did when I executed using the
BIDS debugger and the command line.
Note See Professional SQL Server 11 Integration Services by Michael Coles and
Francis Rodrigues (Apress, 2012) for more information about the Execute Package
Utility .
The SQL Server 2014 Integration Ser-
vices Service
The SQL Server Integration Services 11.0 service installs with SQL Server 2014. To
connect, open SQL Server Management Studio (SSMS). If prompted to connect with
the Connect To Server window at SSMS startup, make sure Server Type is set to Integ-
ration Services. Enter the name of the server in the Server Name drop-down. Please
note there aren't named instances of SSIS: there's one per server (for now, anyway).
You can also enter localhost to connect to the local server's default instance of SSIS.
Once the connection is configured, click the Connect button. Navigate to the pack-
age you desire to execute. SSIS packages stored in the file system or the MSDB data-
base can be executed from the SSIS 2014 service.
SQL Server 2014 provides a new way to manage and execute Integration Services
packages: Integration Services catalogs. We explore this method next.
Integration Services Catalogs
You can only manage SSIS projects that use the project deployment model in Integra-
tion Services catalogs. To execute a package in the catalog, use SSMS to connect to the
instance of SQL Server hosting the SSISDB database. Expand the Integration Services
Catalogs node and then expand the SSISDB node. Drill into the folder containing the
SSIS project and package(s). Right-click the package you wish to execute and click
Execute, as shown in Figure 2-1 .
 
Search WWH ::




Custom Search