May 18, 2012 at 6:21 pm
I have two jobs running in SQL server, each takes about an hour and few mins to complete when run one after the other. The thing about these jobs are they read from the same remote source and write to the same target, what i mean is, over all they have the same configurations. What I did was,scheduled both the jobs to run at the same time in parallel,surprisingly both jobs completed at around the same span of time if they were to run individually. Now my question, this is a huge time gain,but i am sure it comes with a cost. Network bandwidth and exp. log growth come first to my head but I want to know in detail as to what are the other implications if any of running multiple jobs parallely and whether it is wise and acceptable SQL-Ly.
May 18, 2012 at 7:57 pm
It all depends on exactly what the jobs are doing. You're basically seeing maximum concurrency (or close to it at least). We need to know a lot more details and specifics of what these jobs are doing (T-SQL, sources, etc.).
May 19, 2012 at 2:00 am
Thomas Striinger (5/18/2012)
It all depends on exactly what the jobs are doing. You're basically seeing maximum concurrency (or close to it at least). We need to know a lot more details and specifics of what these jobs are doing (T-SQL, sources, etc.).
Thomas, one of the job is a single packagea (big table full extraction) doing a bulk insert into sql table from SAP where as the other job consists of around 100 packages doing a bulk insert to heap sql table. When two jobs run in parallel such as these,do they read/write in parallel as well? what are the other implications?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply