Database maintenance plan: .trn file not backed up

We have installed an SQL 2000 database over a Windows 2000
server platform. We have used the database maintenance
plan wizard to back up three databases on a daily basis.
We have been able to back up the .BAK files, but not
the .TRN files. In addition, a failure message has been
generated to the SQthe "Jobs" module
See my reply to your post int he other group. Please don't multipost.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"apm2524" <anonymous@.discussions.microsoft.com> wrote in message
news:8fd901c432fb$ce8ca380$a101280a@.phx.gbl...
> We have installed an SQL 2000 database over a Windows 2000
> server platform. We have used the database maintenance
> plan wizard to back up three databases on a daily basis.
> We have been able to back up the .BAK files, but not
> the .TRN files. In addition, a failure message has been
> generated to the SQthe "Jobs" module
|||Do not use the daily plan but use the weekly and tick all seven days if need be. For some reason 'Daily' is not quite what it seems, as it is more of a 'one off' than a schedule.

Database maintenance plan: .trn file not backed up

We have installed an SQL 2000 database over a Windows 2000
server platform. We have used the database maintenance
plan wizard to back up three databases on a daily basis.
We have been able to back up the .BAK files, but not
the .TRN files. In addition, a failure message has been
generated to the SQthe "Jobs" moduleSee my reply to your post int he other group. Please don't multipost.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"apm2524" <anonymous@.discussions.microsoft.com> wrote in message
news:8fd901c432fb$ce8ca380$a101280a@.phx.gbl...
> We have installed an SQL 2000 database over a Windows 2000
> server platform. We have used the database maintenance
> plan wizard to back up three databases on a daily basis.
> We have been able to back up the .BAK files, but not
> the .TRN files. In addition, a failure message has been
> generated to the SQthe "Jobs" module|||Do not use the daily plan but use the weekly and tick all seven days if need
be. For some reason 'Daily' is not quite what it seems, as it is more of a
'one off' than a schedule.

Database Maintenance Plan Issue with non-default instances

I have a SQL Server (2000 sp3) with one default instance and many named
instances. I have configured, tested, and monitored a database maintenance
plan for the default instance - works fine. I can't seem to get any of the
default instances to perform the maintenance plan. I have examined the logs,
but I don't see any any relevant entries (I just tried to kick off the job
manaully by executing the associated SQL job). I do see one message in the
log across all of the named instances I tried to run the maintenance plan
against, "Using 'xpsqlbot.dll' version '2000.80.194' to execute extended
stored procedure 'xp_qv'". I have googled this message, but I came up empty.
I should also note that the maintenance plan isn't even writing the history
report.
The only difference I'm aware of is that I performed a 'minimum install' on
the named instances. My transaction logs are growing and growing. The only
way I know to keep the size of these in check is to back them up. Please help
if you can.
Thank you,
- Johnny
Hi
It is not clear how you are running this maintenance plan, and if you
created a different plan in the other instances (which if you did will
probably have a different Ids).
You may want to use create a job that calls xp_slqmaint and specifies the
database and options separately rather than in a plan.
John
"JohnnyMagz" wrote:

> I have a SQL Server (2000 sp3) with one default instance and many named
> instances. I have configured, tested, and monitored a database maintenance
> plan for the default instance - works fine. I can't seem to get any of the
> default instances to perform the maintenance plan. I have examined the logs,
> but I don't see any any relevant entries (I just tried to kick off the job
> manaully by executing the associated SQL job). I do see one message in the
> log across all of the named instances I tried to run the maintenance plan
> against, "Using 'xpsqlbot.dll' version '2000.80.194' to execute extended
> stored procedure 'xp_qv'". I have googled this message, but I came up empty.
> I should also note that the maintenance plan isn't even writing the history
> report.
> The only difference I'm aware of is that I performed a 'minimum install' on
> the named instances. My transaction logs are growing and growing. The only
> way I know to keep the size of these in check is to back them up. Please help
> if you can.
> Thank you,
> - Johnny

Database Maintenance Plan Issue with non-default instances

I have a SQL Server (2000 sp3) with one default instance and many named
instances. I have configured, tested, and monitored a database maintenance
plan for the default instance - works fine. I can't seem to get any of the
default instances to perform the maintenance plan. I have examined the logs,
but I don't see any any relevant entries (I just tried to kick off the job
manaully by executing the associated SQL job). I do see one message in the
log across all of the named instances I tried to run the maintenance plan
against, "Using 'xpsqlbot.dll' version '2000.80.194' to execute extended
stored procedure 'xp_qv'". I have googled this message, but I came up empty.
I should also note that the maintenance plan isn't even writing the history
report.
The only difference I'm aware of is that I performed a 'minimum install' on
the named instances. My transaction logs are growing and growing. The only
way I know to keep the size of these in check is to back them up. Please hel
p
if you can.
Thank you,
- JohnnyHi
It is not clear how you are running this maintenance plan, and if you
created a different plan in the other instances (which if you did will
probably have a different Ids).
You may want to use create a job that calls xp_slqmaint and specifies the
database and options separately rather than in a plan.
John
"JohnnyMagz" wrote:

> I have a SQL Server (2000 sp3) with one default instance and many named
> instances. I have configured, tested, and monitored a database maintenance
> plan for the default instance - works fine. I can't seem to get any of the
> default instances to perform the maintenance plan. I have examined the log
s,
> but I don't see any any relevant entries (I just tried to kick off the jo
b
> manaully by executing the associated SQL job). I do see one message in the
> log across all of the named instances I tried to run the maintenance plan
> against, "Using 'xpsqlbot.dll' version '2000.80.194' to execute extended
> stored procedure 'xp_qv'". I have googled this message, but I came up empt
y.
> I should also note that the maintenance plan isn't even writing the histor
y
> report.
> The only difference I'm aware of is that I performed a 'minimum install' o
n
> the named instances. My transaction logs are growing and growing. The only
> way I know to keep the size of these in check is to back them up. Please h
elp
> if you can.
> Thank you,
> - Johnny