Scheduled jobs overlapping

Greetings,
I have Full database backup job scheduled at 02:00 every day,
Differential backup every 2 hours from 00:00:00 to 23:59:59 and Log
backup every 15 min from 00:00:00 to 23:59:59. Is there a way to control
order of execution, for example: Full backup starts before Differential
backup and Differential backup starts before transaction log backup.
Does Schedule_id plays any role in processing order? Any advise
appreciated.

Aleksandar Andjelkovic

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!<Aleksandar Andjelkovic> wrote in message
news:40b6fc5a$0$208$75868355@.news.frii.net...
> Greetings,
> I have Full database backup job scheduled at 02:00 every day,
> Differential backup every 2 hours from 00:00:00 to 23:59:59 and Log
> backup every 15 min from 00:00:00 to 23:59:59. Is there a way to control
> order of execution, for example: Full backup starts before Differential
> backup and Differential backup starts before transaction log backup.
> Does Schedule_id plays any role in processing order? Any advise
> appreciated.
>
> Aleksandar Andjelkovic
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

You could look at having multiple steps in the same job, or using
sp_help_job to check the status of other jobs before continuing, but the
easiest solution might be to use multiple schedules for each job:

Job1: Full - 02h00
Job2: Differential (Schedule 1) - 00h00
Job2: Differential (Schedule 2) - 04h00 to 23h59, every two hours
Job3: Log (Schedule 1) - 00h15 to 23h59, every hour
Job3: Log (Schedule 2) - 00h30 to 23h59, every hour
Job3: Log (Schedule 3) - 00h45 to 23h59, every hour
Job3: Log (Schedule 4) - 01h00 to 23h59, every 2 hours

You don't need a differential backup at 02h00 because you have the full one
at that time anyway. The multiple log schedules will overlap to backup at
15, 30 and 45 minutes past the hour every hour, and backup on each hour
alternates between differential and log - there's probably no point in
doing both at the same time.

Personally, this seems rather complicated to me, and I would only use
differential once or at most twice a day, with a full backup daily or
weekly, but I don't know your environment or requirements, so the schedule
you've described may well be the best one for you.

Simon

Schedule a Job - Access denied

Greetings,
We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a job
that writes data to a text file. This job works fine either manually or
scheduled when writing to a local hard drive. However when writing to the
network the job will work when run manually but not when run scheduled.
I thought the problem has to do with the scheduler not having rights on the
network. The scheduler runs from the system account. When I tried to change
it to a network account I got this message, "Service Schedule could not be
configured to run under a shared process. If computer xxxx in not a Windows
2000 computer, service which run in a shared process must run under the
system account."
Error 1057: the account name is invalid or does not exist, or the password
is invalid for the account name specified.
Any idea how I can get this schedule job to write to the network?
Jim
Jim,
Which service did you change? You need to change the account of the
SQLServerAgent service to use a domain account that has rights to your
network resource.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602X.html
"Jim" wrote:

> Greetings,
> We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a job
> that writes data to a text file. This job works fine either manually or
> scheduled when writing to a local hard drive. However when writing to the
> network the job will work when run manually but not when run scheduled.
> I thought the problem has to do with the scheduler not having rights on the
> network. The scheduler runs from the system account. When I tried to change
> it to a network account I got this message, "Service Schedule could not be
> configured to run under a shared process. If computer xxxx in not a Windows
> 2000 computer, service which run in a shared process must run under the
> system account."
> Error 1057: the account name is invalid or does not exist, or the password
> is invalid for the account name specified.
> Any idea how I can get this schedule job to write to the network?
> Jim
>
>

Schedule a Job - Access denied

Greetings,
We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a job
that writes data to a text file. This job works fine either manually or
scheduled when writing to a local hard drive. However when writing to the
network the job will work when run manually but not when run scheduled.
I thought the problem has to do with the scheduler not having rights on the
network. The scheduler runs from the system account. When I tried to change
it to a network account I got this message, "Service Schedule could not be
configured to run under a shared process. If computer xxxx in not a Windows
2000 computer, service which run in a shared process must run under the
system account."
Error 1057: the account name is invalid or does not exist, or the password
is invalid for the account name specified.
Any idea how I can get this schedule job to write to the network?
JimJim,
Which service did you change? You need to change the account of the
SQLServerAgent service to use a domain account that has rights to your
network resource.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602_.html
"Jim" wrote:

> Greetings,
> We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a jo
b
> that writes data to a text file. This job works fine either manually or
> scheduled when writing to a local hard drive. However when writing to the
> network the job will work when run manually but not when run scheduled.
> I thought the problem has to do with the scheduler not having rights on th
e
> network. The scheduler runs from the system account. When I tried to chang
e
> it to a network account I got this message, "Service Schedule could not be
> configured to run under a shared process. If computer xxxx in not a Window
s
> 2000 computer, service which run in a shared process must run under the
> system account."
> Error 1057: the account name is invalid or does not exist, or the password
> is invalid for the account name specified.
> Any idea how I can get this schedule job to write to the network?
> Jim
>
>

Schedule a Job - Access denied

Greetings,
We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a job
that writes data to a text file. This job works fine either manually or
scheduled when writing to a local hard drive. However when writing to the
network the job will work when run manually but not when run scheduled.
I thought the problem has to do with the scheduler not having rights on the
network. The scheduler runs from the system account. When I tried to change
it to a network account I got this message, "Service Schedule could not be
configured to run under a shared process. If computer xxxx in not a Windows
2000 computer, service which run in a shared process must run under the
system account."
Error 1057: the account name is invalid or does not exist, or the password
is invalid for the account name specified.
Any idea how I can get this schedule job to write to the network?
JimJim,
Which service did you change? You need to change the account of the
SQLServerAgent service to use a domain account that has rights to your
network resource.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602­.html
"Jim" wrote:
> Greetings,
> We have a NT4.0 SP6a server with SQLServer 7.0 SP3 installed. We have a job
> that writes data to a text file. This job works fine either manually or
> scheduled when writing to a local hard drive. However when writing to the
> network the job will work when run manually but not when run scheduled.
> I thought the problem has to do with the scheduler not having rights on the
> network. The scheduler runs from the system account. When I tried to change
> it to a network account I got this message, "Service Schedule could not be
> configured to run under a shared process. If computer xxxx in not a Windows
> 2000 computer, service which run in a shared process must run under the
> system account."
> Error 1057: the account name is invalid or does not exist, or the password
> is invalid for the account name specified.
> Any idea how I can get this schedule job to write to the network?
> Jim
>
>