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.
http://msdn.microsoft.com/en-us/library/ms141766.aspx
How can you create the catalog before installing the services/tools?
This URL in Missing components section, gives answer:
http://www.sqlhammer.com/blog/running-ssis-packages-in-32-bit/
1. Framework
2. Engine + SSIS + SQL Server Data Tools
3. Create SSIS catalog
???
right i agree. before installing sql server (engine,…) you need to install the .net framwork, bacause it is a NEW server. after fullfilling the requirements, you can istall the dbenginge and ssis. in this case, to run 32bit packages with SSDT. last step should be the creation of the SSIS Catalog.
modify the MsDtsSrvr.ini.xml is incorrect, because you should deploy your packages in the SSIS Catalog not in the MSDB
what a crappy question you could answer with a 1000 scenarios..
if they mean that we ll need to do stuff from the 2012 server then
Engine + SSIS + SQL Server Data Tools
Framework
Create SSIS catalog
otherwise we could go with others answer and i ll find a reason for it ..
171472 521595I adore the look of your web site. I recently built mine and I was searching for some suggestions for my website and you gave me a couple of. Might I ask you whether you developed the web site by youself? 109231
Why do I need SQL Server Data Tools? For project deployment I can use SSMS.
To deploy the packages I guess.
The Logical answer would be:
1/ The .Net 3.5 SP1 installation as it is a prerequisite for the SQL Suite Installation
2/ Installation of the DB Engine and so On including the SSDT (For deployment purposes)
3/ Create the SSIS Catalog
The creation of the catalog cannot be done prior to the installation of the DB Engine. Please refer to:
https://msdn.microsoft.com/en-us/library/gg471509(v=sql.110).aspx
I agree
question is misleading. since there are custom 32bit components, we need 32bit dtutil to run packages in 32bit mode that come with either sql server data tools or client tools. .net framework is prerequisite and we need to install ssis catalog .
install Framework
install Engine, SSIS and SSDT
create SSIS Catalog
what to answer in the exam?
I agree
install Framework
install Engine, SSIS and SSDT
create SSIS Catalog
my exam is in three days and I am not sure if the original answers correct!!!
I am with KRM, what to answer in EXAM?
it is not the only qustion with not the acceptable answer “for me”
I still don’t understand the SSDT requirement. There are two noteworthy features here.
1. Need to run 32 bit components
2. Need to run custom components
Here is a blurb on 32 bit components
In order to prevent the SQL Agent error given as an example above, you will need to install either the Business Intelligence Development Studio (2008), SQL Server Data Tools (2012), or Client Tools (MSDN). I prefer to install the Client Tools when dealing with production servers.
So, you can install ssdt, or client tools which includes the dtexec to run 32 bit. Why must we install ssdt? Must you have SSDT for feature 2? Why not the Client SDK which clearly states:
Client Tools SDK to install managed assemblies for Integration Services programming.
https://technet.microsoft.com/en-us/library/ms143731(v=sql.105).aspx
http://fetchmytip.blogspot.com/2013/06/what-is-sql-client-connectivity-sdk-in.html
No. The Client SDK is to write programs to run ssis things programmatically, not to manage assemblies that are created when you program for IS with like a script task or script component. They’re not super clear. I guess we’re back to the SSDT band wagon on this one.
So which answer is correct?
I think the answer given is correct: as it is win 2008 R2 server there will be already .net framework 3.5 SP1 available. only thing is the sequence you need to install the
1. engine+SSDT+Int services
2. and then create Catalog
3. and then change the msdtssrvr.ini.xml
The last step is needed as the question tells that it is a new server for SSIS only and the database instance may not be in this server ,so in order to configure the database instances for SSIS we need to modifiy msdtssrvr.ini.xml.
but you also need to enable .NET 3.5
https://blogs.msdn.microsoft.com/sqlblog/2010/01/08/how-to-installenable-net-3-5-sp1-on-windows-server-2008-r2-for-sql-server-2008-and-sql-server-2008-r2/
so 4 steps?
do we really need msdtssrvr.ini.xml?
The correct answer should be:
1) Install .Net 3.5 framework with SP1 (as Win 2008 Server R2 just has .Net 3.5 framework)
2) Install db engine, SSIS, SSDT (SSDT complete is required for 32 bit components to be installed, SSMS basic will not suffice)
3) Create SSISDB catalog (for obvious reasons)
I’ve been reading some of the proposed answers in the section comments, and honestly it is driving me crazy when i see some folks including the configuration of the file msdtssrc.ini.xml in order to deploy packages on a named instance.
Just as a reminder, when we deploy SSIS packages to server, they’re stored automatically in the DEFAULT INSTANCE, in the msdb database, and we intent to deploy the SSIS packages to a named instance we modify the file msdtssrc.ini.xml
If we read the question thoroughtly, we’ll find no mention of where the SSIS packages should be stored, or there was a need to store the packages on a named instance, so the answer “and then change the msdtssrvr.ini.xml” is to cross down.
The question was plainly asking for the minimum components to install on the new server to be able to run 32-bits packages.
So the most appropriate answer is :
1) Install .Net 3.5 framework with SP1 (which is a pre-requisite for SSIS tools)
2) Install db engine, SSIS, SSDT (if the packages were in 64 bits i would definetly go for Management tools – basic, but here we have 32 bits packages so SSDT is a must to configure packages on 32 bit runtime mode)
3) Create SSISDB catalog (No way to deploy packages on Intergration Catalogs without the [SSISDB] Catalog)