DRAG DROP
You are developing a SQL Server Integration Services (SSIS) package that downloads data
from a Windows Azure SQL Database database.
A stored procedure will be called in an Execute SQL task by using an ODBC connection.
This stored procedure has only the @CustomerID parameter of type INT.
A project parameter named CustID will be mapped to the stored procedure parameter
@CustomerID.
You need to ensure that the value of the CustID parameter is passed to the @CustomerID
stored procedure parameter.
In the Parameter Mapping tab of the Execute SQL task editor, how should you configure the
parameter? (To answer, drag the appropriate option or options to the correct location or
locations in the answer area.)
Answer: 
Parameter Name should be @CustomerID
0
0
No, ODBC doesn’t support parameter name.
But, why 1 and not 0?
0
0
Uhm, maybe ODBC support parameters name xD
0
0
I tried just now, ParameterName must be 1.
0 or the name of the parameter in the stored procedure doesn’t work.
The answer is right
0
0
yes is correct
https://msdn.microsoft.com/en-us/library/ms140355.aspx
Connection type Parameter name
————————————————-
ADO Param1, Param2, …
ADO.NET and SQLMOBILE @
ODBC 1, 2, 3, …
EXCEL and OLE DB 0, 1, 2, 3, …
0
0
Is it $project::custid or user::custid?. i think it should be user::custid
0
0
“project parameter named CustID”
0
0
“You need to ensure that the value of the CustID parameter is passed to the @CustomerIDstored procedure parameter”
Direction should be output?
0
0
I agree with previous comments, that the above answer is correct.
@John…..the Direction is “Input” and “not Output” according to the question @CustomerID parameter INT is of input direction and not output. The stored_procedure needs to receive the @CustomerID parameter in order to work. So the above answer is correct.
0
0
I also thought the variable name should be @CustomerID but now I see the given answer is correct.
“A project parameter named CustID will be mapped to the stored procedure parameter @CustomerID”
0
0