Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-02-15 : 08:45:06
|
| Rob writes "I am trying to find an answer to what I think is a simple question I think that I am just overlooking this. I have looked on your site, the manual, swynk, sqlteam, and SQLMag and I just can not seem to find this. The question is this: How many jobs can I run at once? and can I change this number? What I am thinking of attempting (and maybe my thinking is wrong) but I have several jobs that I want to run nightly at the same time because I have a very limited maintenance window. If I have 5 jobs that I would like to kick off at 2:30 AM, do they all run at 2:30 AM? if not how can I make them all run at the same time? I realize that this may impact performance but I think that we csan throw some more hardware at it and solve some performance issues.Thanks" |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-02-15 : 09:36:20
|
| I haven't come across a limit of the number of jobs you can run at one time. I have scheduled as many as 10 to kick off all at the same time. This extends each of their run times a little bit, but as long as they aren't super resource intensive, this shouldn't be a problem.Jeff BanschbachConsultant, MCDBA |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-15 : 11:51:35
|
| It depends on what the jobs do as well. If you are doing a full backup with one, and a DBCC checkDb with another, they can't run concurrently.HTH-Chad |
|
|
|
|
|
|
Concurrent Jobs