CORRECT TEXT
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 reading committed 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: See the explanation
Explanation:
Select “IsolationLeve as Choas”
IsolationLevel: readcommitted
TransactionOption: required
0
0
I think isolationlevel should be chaos:
https://social.msdn.microsoft.com/Forums/en-US/0ac06468-3dac-4f24-b65f-0edf08df27af/difference-between-isolation-levels?forum=adodotnetdataproviders
Chaos
Behaves the same way as ReadUncommitted, but checks the isolation level of other pending transactions during a write operation so that transactions with more restrictive isolation levels are not overwritten.
0
0
ReadCommited and Required.
Chaos should not be used if you need to do roll back
0
0