HomeSQLServerPedia SyndicationParallel execution in SSIS

Comments

Parallel execution in SSIS — 7 Comments

  1. I have a parent package running mutiple children packages (about 20). The MaxConcurrentExecutables is set to -1, Children processes Execute in process.
    SQL Server 2008 R2, 64 bit server. When I run the parent package I get the following ERROR Error: Error 0xC0011008 while preparing to load the package. Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.
    When I set the MaxConcurrentExecutables to 1 or 2 the jobs runs fine, but beyond that it fails on arbitary children packages.

    Could you point out what mistake I might be doing? I need to gain performance by running the packages in parallel.

  2. “the child package to be executed can be run in-process or out-of-process by use of the ExecuteOutOfProcess property”

    unfortunately I don’t think setting ExecuteOutOfProcess to true makes it run asynchronously. It’s a bit of a misleading property. You have to use an ExecuteProcess task to accomplish true Parallel execution.

  3. Hello James,
    I have a package, where in db table, it has 10 rows. I want to achive parallel processing of each row with the help of sepearte tasks. I am also not sure how many parallel task i need to add to package to achive this. Is it possible? if yes, pls guide.

  4. Interesting thread (no pun intended).

    I recently encountered an issue with a Data Flow component in one of our legacy packages. The data source pulled from a simple procedure that returned a mid-sized rowset from several joins. The issue turned out to be that parallelism was causing the query to clock itself.

    When run at night with many other jobs, (the theory is that) resource contention caused less threads to be used and the package succeeds. During the day, we could see many threads being spawned and blocking the same spid at the DB level.
    We are experimenting with MAXDOP(1) hint in the query, which seems to resolve the problem.

    I am curious if setting the EngineThreads to 1 in the Data Flow tasks would have the same effect? There are considerations like parent packages that make it tough to isolate specific task settings for iterative testing. Does anyone have direct experience with similarities (or differences) between a MAXDOP setting in the query vs. an EngineThreads setting in the package task?

  5. Scenario : Need to build a package which loads the data from the flat file to the target tables in Oracle database with time stamp + milliseconds as data type for one of the field.

    We were able to build the package and load the data with the datatype as timestamp for that specific column however we were not able to load the data with the timestamp + milliseconds datatype.

    Could some one help me out here

    Regards
    Srivatsav

Leave a Reply

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

HTML tags allowed in your comment: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>