June 10, 2008 at 12:22 pm
Hi,
I have a pretty simple SSIS package that exports some result sets to an excel file. It works fine, but the Pre-Execute phase takes around 5 minutes to complete for some reason.
It just hangs at this message:
Information: 0x40043007 at Export Data, DTS.Pipeline: Pre-Execute phase is beginning.
After a few minutes everything runs fine, but I can't explain why it's taking so long. The export itself just takes a second or two. Anywhere I can look to see what the problem is or anyone have any insight?
Thanks in advance.
June 10, 2008 at 12:46 pm
During the pre-execute, data is gathered and cached on a number of components. If you are using some lookups in full cache mode, for instance, the cache is built during this phase. Also, queries for data sources are run and wait for results to return before execution begins.
So, it could be that you have a query that takes awhile to return data or have a very large cache.
July 11, 2008 at 3:26 pm
Where or how do you turn this off or change the cache setting in SSIS? I am not seeing exactly where to manipulate this?
December 9, 2009 at 4:52 am
Has anyone found a solution to this problem? I am running SSIS packages querying tables with literally billions of rows. The pre execution phase takes longer than the queries. I've found in other forums that the pre execution phase scans the whole table. What is the point in that? I have delayed validation and turned ValidataExternalMetadata to False, but still the package takes ages to start processing data.
What can be done?
Many thanks
Ian
December 9, 2009 at 7:15 am
[font="Comic Sans MS"]
Delay validation has nothing to do with runtime performance - it just doesn't validate the component till runtime.
Did you check this : a detailed discussion on why pre-execute steps might take a while.
[/font]
[font="Comic Sans MS"]--
Sabya[/font]
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply