Which three actions should you perform in sequence?

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.)

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

Explanation:
Box 1: Create the SSIS catalog.
Box 2:

Box 3:

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.



Leave a Reply 5

Your email address will not be published. Required fields are marked *


cao

cao

Install Microsoft .Net Framework 5.3 SP1
Install Database Engine Services, Integration Services, and SQL Server Data Tools.
Create the SSIS catalog

Slazenjer_m

Slazenjer_m

The new server is neither a DEV or TEST server; it would not be used for design, maintenance, or testing of SSIS components; so, there’s no need to install SSDT on the server.

**The server would ONLY deploy and run the packages:

1. OS is Windows Server 2008 R2; need to install .NET 3.5 SP1

**SSISDB needs to be configured (basic SSMS functionality); SSIS packages need to be deployed:

2. Install Database Engine Services, Integration Services, and Management Tools -Basic

3. Lastly, create the SSIS catalog

Min

Min

agreed. how do we create SSIS catalogue without installing management Tools?
but question is a bit tricky. no answer to choose for Some of these SSIS packages use 32-bit custom components.

Slazenjer_m

Slazenjer_m

Just realized ‘some 32-bit custom components’ would be deployed with the SSIS packages.

To deploy SSIS custom task or component, one needs to copy its assembly to the ‘SSIS Task or Component Folders’ and then register it in the Global Assembly Cache.

Essentially, SSDT needs be installed.

raminder

raminder

The question specifies..
‘You need to install only the components that are required to deploy and run the packages’

SSDT is not needed to deploy or Run the package in Prod.
In order to copy and register a 32 bit component we do not need SSDT
Or I am missing something ?

What the correct Answer?