Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Long delay beween job start and actual package execution. Expand / Collapse
Author
Message
Posted Wednesday, May 7, 2014 6:14 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, November 10, 2014 11:57 PM
Points: 17, Visits: 140
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
Post #1568406
Posted Wednesday, May 7, 2014 6:36 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:22 AM
Points: 14,205, Visits: 28,534
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
The Scary DBA
Author of:
SQL Server Query Performance Tuning
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1568417
Posted Wednesday, May 7, 2014 6:42 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 12:52 PM
Points: 13,636, Visits: 11,509
Did you use the Verbose logging level in the SSIS catalog?
What if you set DelayValidation to true in the package?




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1568425
Posted Wednesday, May 7, 2014 6:50 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, November 10, 2014 11:57 PM
Points: 17, Visits: 140
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 :) )
Post #1568432
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse