You are developing a SQL Server Integration Services (SSIS) project that contains a project
Connection Manager and multiple packages.
All packages in the project must connect to the same database. The server name for the
database must be set by using a parameter named ServerParam when any package in the
project is executed.
You need to develop this project with the least amount of development effort.
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)
A.
Set the Sensitive property of the parameter to True.
B.
Edit each package Connection Manager. Set the ServerName property to
@[$Project::ServerParam].
C.
Edit the project Connection Manager in Solution Explorer. Set the ServerName property
to @[$Project::ServerParam].
D.
Create a project parameter named ServerName.
E.
Create a package parameter named ServerName in each package.
F.
Set the Required property of the parameter to True.
Explanation:
B: From question: ” The server name for the database must be set by using a parameter named ServerParam when
any package in the project is executed.”
D: SSIS 2012 has introduced the concept of Project level connection managers. An SSIS
project is generally more than one package. To simplify lives, the SSIS team now allows for
the sharing of common resources across projects, connection managers being one of those
resources.
F: When a parameter is marked as required, a server value or execution value must be
specified for that parameter. Otherwise, the corresponding package does not execute.
Although the parameter has a default value at design time, it will never be used once the
project is deployed.
Note:
* Integration Services (SSIS) parameters allow you to assign values to properties within
packages at the time of package execution. You can create project parameters at the project
level and package parameters at the package level. Project parameters are used to supply
any external input the project receives to one or more packages in the project. Package
parameters allow you to modify package execution without having to edit and redeploy the package.
Reference: Integration Services (SSIS) Parameters
I think the ‘ServerName’ should be changed to ‘ServerParam’ in option D.
Otherwise, it makes no sense to create a project parameter ‘ServerName’ in this case.
0
0
I think its CDF because any package can read the project connection manager to a server.
1
0
CDF
1
0
“The server name for the database must be set by using a parameter named ServerParam”
Answer is CF.
Answer D does not make sense: We should have only one project parameter named ServerParam that map the property SERVERNAME of the project connection manager.
0
0
You read the question as the parameter serverparam has already been created, so why make another one with the same name in choice D. Poor bastard. This is an instance of poor question writing again. More likely than not, but not always, when a question says use x to do y, you have to make x and do y. Here option d is x and option c is y. And then you need f because you need it.
0
0
CDF
0
0
CDF
0
0
Questions says: Your Developing….(SSIS) project that contains “project Connection Manager” so the correct answer is;
CDF
0
0
CDF
0
0
Agreed, CDF, although the wording is a bit unclear and the param name in option D looks wrong.
0
0
Option C refer to parameter name ‘Project::ServerParam’, but option D creates parameter ‘ServerName’. Both C and D cannot be taken together as parameter name differ.
I think it’s C and F taking into consideration that parameter ServerParam is already created, as suggested in question.
0
0