You need to ensure that all the execution trees run in parallel

You are performance tuning a SQL Server Integration Services (SSIS) package to load sales data from a
source system into a data warehouse that is hosted on Windows Azure SQL Database. The package
contains a data flow task that has 10 source-to-destination execution trees.
Only five of the source-to-destination execution trees are running in parallel.
You need to ensure that all the execution trees run in parallel.
What should you do?

You are performance tuning a SQL Server Integration Services (SSIS) package to load sales data from a
source system into a data warehouse that is hosted on Windows Azure SQL Database. The package
contains a data flow task that has 10 source-to-destination execution trees.
Only five of the source-to-destination execution trees are running in parallel.
You need to ensure that all the execution trees run in parallel.
What should you do?

A.
Add OnError and OnWarning event handlers.

B.
Create a new project and add the package to the project.

C.
Query the ExecutionLog table.

D.
Add an Execute SQL task to the event handlers.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


Noel

Noel

all answers wrong.
Set the EngineThreads property of the data flow task to 10.

Anna

Anna

https://msdn.microsoft.com/en-us/library/ms141031.aspx

To support parallel execution of different tasks in the package, Integration Services uses two properties: MaxConcurrentExecutables and EngineThreads.

The MaxConcurrentExecutables property is a property of the package itself…To understand how this property works, consider a sample package that has three Data Flow tasks. If you set MaxConcurrentExecutables to 3, all three Data Flow tasks can run simultaneously. However, assume that each Data Flow task has 10 source-to-destination execution trees. Setting MaxConcurrentExecutables to 3 does not ensure that the execution trees inside each Data Flow task run in parallel.

The EngineThreads property is a property of each Data Flow task. This property defines how many threads the data flow engine can create and run in parallel. The EngineThreads property applies equally to both the source threads that the data flow engine creates for sources and the worker threads that the engine creates for transformations and destinations. Therefore, setting EngineThreads to 10 means that the engine can create up to ten source threads and up to ten worker threads.
To understand how this property works, consider the sample package with three Data Flow tasks. Each of Data Flow task contains ten source-to-destination execution trees. If you set EngineThreads to 10 on each Data Flow task, all 30 execution trees can potentially run simultaneously.