all groups > sql server (alternate) > october 2004 >
You're in the

sql server (alternate)

group:

Jobs fail when tied together


Jobs fail when tied together watuni2000 NO[at]SPAM yahoo.co.nz
10/14/2004 9:00:24 AM
sql server (alternate):
There is a truncate,backup and move job.
Seperately everything works fine but together
the job fails consistently
The intention here is to let the jobs precede each other.
Is failure when grouped a normal behaviour in sql server or am I missing
something??

TIA

Re: Jobs fail when tied together watuni2000 NO[at]SPAM yahoo.co.nz
10/15/2004 5:43:41 AM
[quoted text, click to view]


The job finally finished and the error was "cannot perform backup or restore
operation within a transaction"

--This is what I will like to do in order

Everthing works seperately but since the order matters
I will ideally like to
1) truncate the transanction log
2)backup the database
3) copy the database to another server.
I like to schedule this so that one precedes the other
Individaully everything works perfect but since the
log needs to be truncated ,before a backup and the
backup needs to finish before a copy
I will appreciate help on how to do

Tried to put all this in order as a single job and it failed


Any help will be greatly appreciated

Re: Jobs fail when tied together Simon Hayes
10/15/2004 11:24:10 AM

[quoted text, click to view]

I'm not sure I understand - do you have 3 job, or one job with 3 steps? How
are you executing them together? And what does "fails" mean? Do you have
some error messages? Also, what version of MSSQL do you have?

Simon

Re: Jobs fail when tied together Simon Hayes
10/15/2004 3:49:31 PM

[quoted text, click to view]

As the error message says, are you doing your backup within a transaction?

In any case, why not backup the database directly to the other server? Then
you can have a job with one single TSQL step which has two commands:

backup log MyDB with truncate_only
backup database MyDB to disk = '\\otherserver\backups\mssql\MyDB.bak'

Or put them into two separate TSQL steps if you like. The MSSQL service
account must have access to the \\otherserver\backups share for this to
work - see "Setting up Windows Services Accounts" and "BACKUP" in Books
Online.

If you don't need the transaction log anyway, you could also put the
database into simple recovery mode, so the log is truncated for you.

Simon

AddThis Social Bookmark Button