May 7, 2014 at 6:14 am
Hello
I have problems sometimes with a package.
There is and SQL Agent job that starts a package (from a file system using cmd command). Usually job takes 8-10 minutes. But sometimes it get stuck for a long time (1+ hour).
DTexec process can be found with procmon, but it seems it just not doing anything (And package is not logging to file Start of the execution) After long wait it just runs a package quickly.
I've moved a package to SSIS catalog to try to get more detailed logging, but with no luck.
Job starts at 1 PM, package execution starts at 1:49 PM. Without any messages about the execution in SSISDB log.
First I've thought it might be long validation problem, but when package executes validation messages are there and they perform quick.
Regards,
Olegas
May 7, 2014 at 6:36 am
Hard to say. Most likely it's some sort of resource contention, blocking, something along those lines. But I'm just guessing. We don't have enough data.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 7, 2014 at 6:42 am
Did you use the Verbose logging level in the SSIS catalog?
What if you set DelayValidation to true in the package?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 7, 2014 at 6:50 am
Delay Validation is beeing changed. Changing for connections other stuff.
Logging is set to basic. But the provlem is that it's not logging anything before execution starts. But will try vebrose logging (need to get a bit more space first. Just in case 🙂 )
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply