You are designing a package control flow. The package moves sales order data from a SQL Azure
transactional database to an on-premise reporting database. The package will run several times a day, while
new sales orders are being added to the transactional database. The current design of the package control flow
is shown in the answer area. (Click the Exhibit button.)
The Insert New Orders Data Flow task must meet the following requirements:
Usage of the tempdb database should not be impacted.
Concurrency should be maximized, while only readingcommitted transactions.
If the task fails, only that task needs to be rolled back.
You need to configure the Insert New Orders Data Flow task to meet the requirements. How should you
configure the transaction properties? (To answer, select the appropriate setting or settings in the answer area.)
Answer:
Explanation:
According to these references, this answer looks correct.
References:
http://msdn.microsoft.com/en-us/library/ms137690.aspx
http://msdn.microsoft.com/en-us/library/ms137749.aspx
http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.dtscontainer.isolationlevel.aspx
http://msdn.microsoft.com/en-us/library/ms173763.aspx
Wrong should be not supported
Its OK Should be Required since there is a condition:
“If the task fails, only that task needs to be rolled back.”
So we must start a new transaction – and to make sure it is started we must have a Required set.