Home Forums Data Warehousing Integration Services 15 seconds pending execution RE: 15 seconds pending execution

  • March 8, 2018 at 10:21 am

    #1982504

    sgmunson - Thursday, March 8, 2018 9:49 AM

    I'd start with having your network team analyze the traffic and see exactly what's going on.   While awaiting that response, I'd search online for any issues with the various KB articles that are part of all your updates.

    Thanks.  I'll shoot some stuff off to my IT guys and see what they can see.
    I did find some KB's but they were all about the certificate revocation list which takes roughly 15 seconds to time out so that was a big red flag, but they suggested blocking it at the firewall (which IT didn't want to do) or blocking it in the hosts file (which is what I ended up doing) but it made no difference.
    Normally I wouldn't be too concerned about a 15 second delay, but we have some SQL jobs that have 30+ steps in them that are all smaller SSIS packages for moving and transforming data.  That adds a lot of extra time onto a data load.

    Thanks for the tip though; I'll poke the IT guys to check out the network traffic and see what is happening.  If that doesn't help, I may need to look at increasing the complexity of our SSIS packages, but I don't like that solution.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.