|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854,
Visits: 4,873
|
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:53 AM
Points: 1,528,
Visits: 359
|
|
thanks Elliott :)
i was looking for various concurrency options in SSIS package, your example has helped me... looking forward for Part 2.
|
|
|
|
|
SSCoach
         
Group: General Forum Members
Last Login: 2 days ago @ 1:07 PM
Points: 18,733,
Visits: 12,332
|
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854,
Visits: 4,873
|
|
Thanks guys, I hope it helps..
CEWII
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, June 17, 2010 11:02 AM
Points: 1,
Visits: 1
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, November 18, 2010 8:24 AM
Points: 12,
Visits: 85
|
|
| Interesting stuff but I tried adding "waitfor delay '00:00:01';" to each of the sample work SQL tasks in the OnePackageMethod (before the update statement). That way you can see what is happening because the work takes longer. On my workstation I observed that none of the tasks executed concurrently. They each execute in turn. Maybe on a server it would behave differently?
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854,
Visits: 4,873
|
|
richard.maw (6/17/2010) Interesting stuff but I tried adding "waitfor delay '00:00:01';" to each of the sample work SQL tasks in the OnePackageMethod (before the update statement). That way you can see what is happening because the work takes longer. On my workstation I observed that none of the tasks executed concurrently. They each execute in turn. Maybe on a server it would behave differently?I've seen wildly varying performance on different machines, and while SSIS will try to run multiple items if the package is built to do that it can't always do it, on a single processor machine (no hyperthreading either) I doubt it will do it. On a server and even a laptop with multiple cores and a couple GB of memory you will see it thread..
Thanks for reading..
CEWII
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, November 18, 2010 8:24 AM
Points: 12,
Visits: 85
|
|
| I have dual core and 4GB. When I get the chance I'll try using a remote SQL Server that should help.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, July 22, 2010 8:59 AM
Points: 110,
Visits: 952
|
|
| This works very well for centralizing a task comprised of steps on remote servers. A package to manage the remote calls has very little overhead on the machine running the package. In our usage there's a server at corporate that calls many colo-hosted SQL instances.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854,
Visits: 4,873
|
|
richard.maw (6/17/2010) I have dual core and 4GB. When I get the chance I'll try using a remote SQL Server that should help.Interesting, I have seen significantly less hardware run 3 threads at a time.
Mike Dougherty (6/17/2010) This works very well for centralizing a task comprised of steps on remote servers. A package to manage the remote calls has very little overhead on the machine running the package. In our usage there's a server at corporate that calls many colo-hosted SQL instances.Good to know, thanks..
CEWII
|
|
|
|