Welcome to dbFreaks.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Maintenance Plans in SQL 2005

  
   Database Help (Home) -> Server RSS
Next:  bulk insert troubles  
Author Message
RG

External


Since: Aug 15, 2008
Posts: 6



(Msg. 1) Posted: Tue Jul 27, 2010 9:25 am
Post subject: Maintenance Plans in SQL 2005
Archived from groups: microsoft>public>sqlserver>server (more info?)
I have 3 jobs in My maintenance plan. The jobs are connected by precedence
constraints. In each case, the constraint is set to completion. It appears
that all the jobs are being executed at the same time. My goal is to execute
the next job as long as the previous job completes, irregardless whether it
fails or succeeds. Any help is appreciated.

Thanks in advance

 >> Stay informed about: Maintenance Plans in SQL 2005 
Back to top
Login to vote
John Bell

External


Since: Jan 11, 2008
Posts: 157



(Msg. 2) Posted: Tue Jul 27, 2010 3:25 pm
Post subject: Re: Maintenance Plans in SQL 2005 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
On Tue, 27 Jul 2010 09:25:02 -0700, RG
wrote:

>I have 3 jobs in My maintenance plan. The jobs are connected by precedence
>constraints. In each case, the constraint is set to completion. It appears
>that all the jobs are being executed at the same time. My goal is to execute
>the next job as long as the previous job completes, irregardless whether it
>fails or succeeds. Any help is appreciated.
>
>Thanks in advance

Hi

The precedence constraint would determine the order that tasks (not
jobs) are executed. Why do you think they are being run in parallel?

John

 >> Stay informed about: Maintenance Plans in SQL 2005 
Back to top
Login to vote
Jeffrey Williams

External


Since: Dec 28, 2008
Posts: 5



(Msg. 3) Posted: Tue Jul 27, 2010 7:58 pm
Post subject: Re: Maintenance Plans in SQL 2005 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
If you are using the Execute SQL Agent Job task - or executing
sp_start_job - then I would expect this behavior. Both of those will return
success if the agent job was started and failure if the job was not started.
These tasks do not wait until completion of the actual agent job.

"John Bell" wrote in message

> On Tue, 27 Jul 2010 09:25:02 -0700, RG
> wrote:
>
>>I have 3 jobs in My maintenance plan. The jobs are connected by
>>precedence
>>constraints. In each case, the constraint is set to completion. It
>>appears
>>that all the jobs are being executed at the same time. My goal is to
>>execute
>>the next job as long as the previous job completes, irregardless whether
>>it
>>fails or succeeds. Any help is appreciated.
>>
>>Thanks in advance
>
> Hi
>
> The precedence constraint would determine the order that tasks (not
> jobs) are executed. Why do you think they are being run in parallel?
>
> John
 >> Stay informed about: Maintenance Plans in SQL 2005 
Back to top
Login to vote
John Bell

External


Since: Jan 11, 2008
Posts: 157



(Msg. 4) Posted: Wed Jul 28, 2010 3:25 am
Post subject: Re: Maintenance Plans in SQL 2005 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
On Tue, 27 Jul 2010 19:58:58 -0700, "Jeffrey Williams"
wrote:

>If you are using the Execute SQL Agent Job task - or executing
>sp_start_job - then I would expect this behavior. Both of those will return
>success if the agent job was started and failure if the job was not started.
>These tasks do not wait until completion of the actual agent job.
>
>"John Bell" wrote in message
>
>> On Tue, 27 Jul 2010 09:25:02 -0700, RG
>> wrote:
>>
>>>I have 3 jobs in My maintenance plan. The jobs are connected by
>>>precedence
>>>constraints. In each case, the constraint is set to completion. It
>>>appears
>>>that all the jobs are being executed at the same time. My goal is to
>>>execute
>>>the next job as long as the previous job completes, irregardless whether
>>>it
>>>fails or succeeds. Any help is appreciated.
>>>
>>>Thanks in advance
>>
>> Hi
>>
>> The precedence constraint would determine the order that tasks (not
>> jobs) are executed. Why do you think they are being run in parallel?
>>
>> John

In that's case he needs to run the package in a task and not execute
the job!

John
 >> Stay informed about: Maintenance Plans in SQL 2005 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Maintenance Plans and corresponding Jobs - SQL Server 2005: Creating a maintenance plan generates a job. Two questions: 1. If I change the job instead of the maintenance plan, will the maintenance plan break? And/or is there a way to get the job and maintenance plan out of sycnh? 2. SQL..

SSIS and Database Maintenance Plans - We are thinking of implementing Database maintenance plans for our SQL 2005 instances. We do not have SSIS installed on the server. Does it require to install SSIS to implement Database Maintenance plan? What is the role of SSIS with Database Maintenance...

SQL2005 - Maintenance Plans Question -

Index Rebuild/Reorg using Maintenance Plans - I created two maintenance plans: one to reorg the indexes on two specific databases and another to rebuild the indexes on those same databases. When I ran a report called Index Physical Stats available from the Standard Reports in SSMS, the report..

Why different execution plans on different 2005 machines? - We've been dealing with this issue for 3 weeks now, and i've gotten tired, frustrated, and as some of you may have noticed: a little cranky. We have an application that we wrote. It runs fine on our development 2005 machine, it runs fine on their tes...
   Database Help (Home) -> Server All times are: Pacific Time (US & Canada)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]