Reputation: 2847
As the question suggests, I'm staring at a transformation that has several control flow elements, many of which are data flows.
Currently, one of the data flow objects within the control flow tab is lit up yellow. When I open that Data Flow object by double click or selecting the "Data Flow" tab, there are no boxes lit up in any color.
This would lead me to believe it's validating, perhaps?
Is there any way to tell what it's doing, and any steps to help make this process faster?
**Edit:
I took a look at the execution, and it looks like it's stuck in the Pre-Execute stage around 50%. Is there any optimization to be done for this stage.
Screenshot of the dataflow that isn't running. (This was taken while the control flow shows this data flow task as yellow)
Upvotes: 3
Views: 5239
Reputation: 7219
Another potential solution (to those like me who come across this question in the future) is to ensure that the component is not using an internal transaction.
I had this happen (all tasks within data flow green, but showing on the control flow as yellow) this morning with a package doing a bulk update. The component I was using had a checkbox to turn on an internal transaction, which was waiting for a response from SQL Server before allowing the data flow to complete.
Look for a checkbox to turn off internal transactions or table locks, and rerun without that.
Upvotes: 1
Reputation: 2847
I broke out each of these chunks into their own DF. One of these DFs was continuing to get stuck on the Pre-Execute stage. I ran the query for that OLE DB Source and found a long running query due to some dropped indexes. Replaced the index, and the transform stopped hanging.
Upvotes: 1
Reputation: 31
Just had a similar problem with a data flow in a SSIS package. No matter how many rows it had to transfer, after it copied all rows, the task remained yellow and there was no data in the destination table (MS SQL Server 2012). I could work-around the problem by dropping the destination table and issue CREATE TABLE/CREATE INDEX again.
Upvotes: 1
Reputation: 1186
If all you're looking for is to identify why it is yellow, view the Error List window and click on Warnings to make them visible if you need to. This should at least confirm if it is just validation, or something else.
Upvotes: 1
Reputation: 613
When you go into the configuration properties of your package and choose 'debugging properties' is it set to run in 'optimized' mode? If so it will be yellow and then turn green/red when done. You need to make sure 'run in optimized' is off and 'interactive mode' is true.
Upvotes: 1