DRAG DROP
A new dedicated server is used to execute resource-intensive SQL Server Integration Services (SSIS) 2012
packages. The environment that you are deploying the packages to has the following constraints:
The operating system is Windows Server 2008 R2.
The SSIS packages are stored in the SSIS catalog.
Some of these SSIS packages use 32-bit custom components.
You need to install only the components that are required to deploy and run the packages on the new
server.
Which three actions should you perform in sequence? (To answer, move the appropriate actions from
the list of actions to the answer area and arrange them in the correct order.)
Answer: See the explanation
Note:
Step 1:
Step 2:
If you require 32-bit versions of the Integration Services runtime and tools to run certain packages in 32-
bit mode, you must also install SQL Server Data Tools (SSDT).
Note:
For a complete installation of Integration Services, together with the tools and documentation for
developing and managing packages, select both Integration Services and the following Shared Features:
* SQL Server Data Tools to install the tools for designing packages.
* Management Tools – Complete to install SQL Server Management Studio for managing packages.
* Client Tools SDK to install managed assemblies for Integration Services programming.Step 3: How to Modify the Service Configuration File to Connect to a Named Instance of SQL Server
To connect to a named instance of SQL Server, you must modify the service configuration file,
MsDtsSrvr.ini.xml.
Install NET Framework
Install Engine and Data Tools
Create SSIS catalog
agree
Do we really need Data tools also?
Windows Server 2008 R2 has already Framework installed.
1. Install Engine and Data Tools
2. Create SSIS catalog
3. Configure MsDtsSrvr.ini.xml