SQL7 and 2000 appear to treat certain failures differently. We typically
define one plan to backup/offload the logs of all databases. If SQL 7
attempts to offload a log whose DB has 'trunc log on checkpoint' set it
ignores the error and carries on, SQL2000 returns an error and the log
offload job is marked as failed. I read KB article Q242500 as saying that
the SQL7 behaviour was due to a bug in SQLMAINT for SQL7, so I guess this
bug has been fixed in SQL2000. Does anyone know this for sure?
We'd assumed the SQL7 behaviour was a feature and this was useful to us as
we sometimes have a mix of 'recovery modes' across our DBs. Looks like for
SQL2000 we may have to code a script to determine which DBs have logs that
can be offloaded (i.e. aren't 'trunc logged') & then attempt to offload only
them.....Thanks.......