Showing posts with label plans. Show all posts
Showing posts with label plans. Show all posts

Monday, March 19, 2012

Database Maintnenance Plan

Good Afternoon
I am using database maintenance plans in order to perform
Backups, including optimisation, index re-builds etc.
The problem is that I have discovered that the Maintenance
Plans do not always perform the Backup, although the rest
of the plans perform normally: -
Two Maintenance Plans performing Full Backup, one at
midday and one in the evening, monday to friday, deleting
old files, re-building indexes, re-sizing databases and
optimising unused space.
Two Maintenance Plans performing Transaction Log Backups,
one from 08:00 to 11:00 and the other 13:00 to 18:, monday
to friday, deleting old files and re-building indexes.
There is plenty of space on the Server to allow for the
Backups. E.g. The drive for the Transaction Log Backups
has over 5Gb of space available, the collective size of
the Backups never total more than 350Mb.
I created these Maintenance Plans, and I am registered on
the SQL Server as a System Administrator.
Thank You In Advance
Tony C.
Make sure that you have specified a report file for the maint plan and check that file for error messages.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Tony C" <anonymous@.discussions.microsoft.com> wrote in message news:20d201c4279b$33e423a0$a601280a@.phx.gbl...
> Good Afternoon
> I am using database maintenance plans in order to perform
> Backups, including optimisation, index re-builds etc.
> The problem is that I have discovered that the Maintenance
> Plans do not always perform the Backup, although the rest
> of the plans perform normally: -
> Two Maintenance Plans performing Full Backup, one at
> midday and one in the evening, monday to friday, deleting
> old files, re-building indexes, re-sizing databases and
> optimising unused space.
> Two Maintenance Plans performing Transaction Log Backups,
> one from 08:00 to 11:00 and the other 13:00 to 18:, monday
> to friday, deleting old files and re-building indexes.
> There is plenty of space on the Server to allow for the
> Backups. E.g. The drive for the Transaction Log Backups
> has over 5Gb of space available, the collective size of
> the Backups never total more than 350Mb.
> I created these Maintenance Plans, and I am registered on
> the SQL Server as a System Administrator.
> Thank You In Advance
>
> Tony C.
|||Thanks for this, the Maintenance Plans were producing the
Logs..
It would seem that one of the Applications we are using
can hold up other Transactions when it is left in a
certain state, I've therefore got a bit of debugging to
do!!
Tony C
>--Original Message--
>Make sure that you have specified a report file for the
maint plan and check that file for error messages.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"Tony C" <anonymous@.discussions.microsoft.com> wrote in
message news:20d201c4279b$33e423a0$a601280a@.phx.gbl...[vbcol=seagreen]
perform[vbcol=seagreen]
Maintenance[vbcol=seagreen]
rest[vbcol=seagreen]
deleting[vbcol=seagreen]
Backups,[vbcol=seagreen]
monday[vbcol=seagreen]
on
>
>.
>

Database Maintenance plans log

I receive every 30 min 5 event into my event viewer application log telling
me something like this
18265 :
Log backed up: Database: UserDatabases, creation date(time):
2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of dump
devices: 1, device information: (FILE=1, TYPE=DISK:
{'H:\SQLBackup\UserDatabases\UserDatabases_tlog_20 0505120800.TRN'}).
Is there a way to remove the log to event viewer from a maintenante plan?
First its not giving anything good and its hard to find error since my event
viewer is full of those information.
Hi
You might be logging it into an Event Viewer. Just try to update the same or
try to remove the logging
best Regards,
Chandra
http://chanduas.blogspot.com/
"fatp" wrote:

> I receive every 30 min 5 event into my event viewer application log telling
> me something like this
> 18265 :
> Log backed up: Database: UserDatabases, creation date(time):
> 2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of dump
> devices: 1, device information: (FILE=1, TYPE=DISK:
> {'H:\SQLBackup\UserDatabases\UserDatabases_tlog_20 0505120800.TRN'}).
>
> Is there a way to remove the log to event viewer from a maintenante plan?
> First its not giving anything good and its hard to find error since my event
> viewer is full of those information.
>
|||Short answer: No. These entries are not written by Maint Plan nor by Agent. They are written by SQL
Server. Each time SQL Server does a backup, it will write that to the eventlog. For other error
messages, you can configure whether they should be written to the eventlog or not, but that
configuration (sp_altermessage) is ignored for backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"fatp" <fatp@.discussions.microsoft.com> wrote in message
news:AC8C5172-D6CA-4E33-8F36-D7D59B822692@.microsoft.com...
> I receive every 30 min 5 event into my event viewer application log telling
> me something like this
> 18265 :
> Log backed up: Database: UserDatabases, creation date(time):
> 2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of dump
> devices: 1, device information: (FILE=1, TYPE=DISK:
> {'H:\SQLBackup\UserDatabases\UserDatabases_tlog_20 0505120800.TRN'}).
>
> Is there a way to remove the log to event viewer from a maintenante plan?
> First its not giving anything good and its hard to find error since my event
> viewer is full of those information.
>

Sunday, March 11, 2012

Database Maintenance plans log

I receive every 30 min 5 event into my event viewer application log telling
me something like this
18265 :
Log backed up: Database: UserDatabases, creation date(time):
2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of dump
devices: 1, device information: (FILE=1, TYPE=DISK:
{'H:\SQLBackup\UserDatabases\UserDatabases_tlog_200505120800.TRN'}).
Is there a way to remove the log to event viewer from a maintenante plan?
First its not giving anything good and its hard to find error since my event
viewer is full of those information.Hi
You might be logging it into an Event Viewer. Just try to update the same or
try to remove the logging
--
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"fatp" wrote:
> I receive every 30 min 5 event into my event viewer application log telling
> me something like this
> 18265 :
> Log backed up: Database: UserDatabases, creation date(time):
> 2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of dump
> devices: 1, device information: (FILE=1, TYPE=DISK:
> {'H:\SQLBackup\UserDatabases\UserDatabases_tlog_200505120800.TRN'}).
>
> Is there a way to remove the log to event viewer from a maintenante plan?
> First its not giving anything good and its hard to find error since my event
> viewer is full of those information.
>|||Short answer: No. These entries are not written by Maint Plan nor by Agent. They are written by SQL
Server. Each time SQL Server does a backup, it will write that to the eventlog. For other error
messages, you can configure whether they should be written to the eventlog or not, but that
configuration (sp_altermessage) is ignored for backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"fatp" <fatp@.discussions.microsoft.com> wrote in message
news:AC8C5172-D6CA-4E33-8F36-D7D59B822692@.microsoft.com...
> I receive every 30 min 5 event into my event viewer application log telling
> me something like this
> 18265 :
> Log backed up: Database: UserDatabases, creation date(time):
> 2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of dump
> devices: 1, device information: (FILE=1, TYPE=DISK:
> {'H:\SQLBackup\UserDatabases\UserDatabases_tlog_200505120800.TRN'}).
>
> Is there a way to remove the log to event viewer from a maintenante plan?
> First its not giving anything good and its hard to find error since my event
> viewer is full of those information.
>

Database Maintenance plans log

I receive every 30 min 5 event into my event viewer application log telling
me something like this
18265 :
Log backed up: Database: UserDatabases, creation date(time):
2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of dum
p
devices: 1, device information: (FILE=1, TYPE=DISK:
& #123;'H:\SQLBackup\UserDatabases\UserDat
abases_tlog_200505120800.TRN'}).
Is there a way to remove the log to event viewer from a maintenante plan?
First its not giving anything good and its hard to find error since my event
viewer is full of those information.Hi
You might be logging it into an Event Viewer. Just try to update the same or
try to remove the logging
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"fatp" wrote:

> I receive every 30 min 5 event into my event viewer application log telli
ng
> me something like this
> 18265 :
> Log backed up: Database: UserDatabases, creation date(time):
> 2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of d
ump
> devices: 1, device information: (FILE=1, TYPE=DISK:
> & #123;'H:\SQLBackup\UserDatabases\UserDat
abases_tlog_200505120800.TRN'}).
>
> Is there a way to remove the log to event viewer from a maintenante plan?
> First its not giving anything good and its hard to find error since my eve
nt
> viewer is full of those information.
>|||Short answer: No. These entries are not written by Maint Plan nor by Agent.
They are written by SQL
Server. Each time SQL Server does a backup, it will write that to the eventl
og. For other error
messages, you can configure whether they should be written to the eventlog o
r not, but that
configuration (sp_altermessage) is ignored for backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"fatp" <fatp@.discussions.microsoft.com> wrote in message
news:AC8C5172-D6CA-4E33-8F36-D7D59B822692@.microsoft.com...
> I receive every 30 min 5 event into my event viewer application log tellin
g
> me something like this
> 18265 :
> Log backed up: Database: UserDatabases, creation date(time):
> 2003/05/31(08:14:32), first LSN: 27:167:1, last LSN: 27:167:1, number of d
ump
> devices: 1, device information: (FILE=1, TYPE=DISK:
> & #123;'H:\SQLBackup\UserDatabases\UserDat
abases_tlog_200505120800.TRN'}).
>
> Is there a way to remove the log to event viewer from a maintenante plan?
> First its not giving anything good and its hard to find error since my eve
nt
> viewer is full of those information.
>

Database Maintenance Plans for Backup

Hello

We created maintenance plans for Backup, we configured as:

1. Backup set expires after 2 days. (but we still see backup files are at the location from day one)

2. There is Overwrite and Append in backup file settings. what eaxactly overwrites means, in case we set up expire the backup set after 2 days.

please advice. Thanks, Jay

If you are using a single backup device (whether it's a tape, file location...it's the same thing), overwrite means it will replace the backup on that device with the current backup. So that device will just hold the one backup. Append means it will add the current backup to the device. That device will hold multiple backups.

If you use a single device, set it to overwrite and the backup has not expired and you have selected the option to check the expiration date of the backup, you will get an error. It is designed to prevent you from accidentally overwritting a backup that you want to keep.

-Sue

database maintenance plans for 2005 Express

Hello:
I know how to create database maintenance plans (automated backups) in SQL
Server 2000 and 2005.
But, I have never done so in SQL Server 2005 Express Edition.
I tried right-clicking on maintenance plans in 2005 Express so that I could
choose to create new plans, but no such selection is available to choose.
So, how do you create maintenance plans in SQL Server 2005 Express Edition?
Thanks!
childofthe1980s
Express doesn't come with SQL Agent. Have a look at these:
http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
Backing up Express
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part II
http://www.sqldbatips.com/showarticle.asp?ID=29
Andrew J. Kelly SQL MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:2FC46958-D2C0-4120-B6C1-583FCE607044@.microsoft.com...
> Hello:
> I know how to create database maintenance plans (automated backups) in SQL
> Server 2000 and 2005.
> But, I have never done so in SQL Server 2005 Express Edition.
> I tried right-clicking on maintenance plans in 2005 Express so that I
> could
> choose to create new plans, but no such selection is available to choose.
> So, how do you create maintenance plans in SQL Server 2005 Express
> Edition?
> Thanks!
> childofthe1980s

database maintenance plans for 2005 Express

Hello:
I know how to create database maintenance plans (automated backups) in SQL
Server 2000 and 2005.
But, I have never done so in SQL Server 2005 Express Edition.
I tried right-clicking on maintenance plans in 2005 Express so that I could
choose to create new plans, but no such selection is available to choose.
So, how do you create maintenance plans in SQL Server 2005 Express Edition?
Thanks!
childofthe1980sExpress doesn't come with SQL Agent. Have a look at these:
http://blogs.msdn.com/rogerwolterbl.../13/575974.aspx
Backing up Express
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part II
http://www.sqldbatips.com/showarticle.asp?ID=29
Andrew J. Kelly SQL MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:2FC46958-D2C0-4120-B6C1-583FCE607044@.microsoft.com...
> Hello:
> I know how to create database maintenance plans (automated backups) in SQL
> Server 2000 and 2005.
> But, I have never done so in SQL Server 2005 Express Edition.
> I tried right-clicking on maintenance plans in 2005 Express so that I
> could
> choose to create new plans, but no such selection is available to choose.
> So, how do you create maintenance plans in SQL Server 2005 Express
> Edition?
> Thanks!
> childofthe1980s

database maintenance plans for 2005 Express

Hello:
I know how to create database maintenance plans (automated backups) in SQL
Server 2000 and 2005.
But, I have never done so in SQL Server 2005 Express Edition.
I tried right-clicking on maintenance plans in 2005 Express so that I could
choose to create new plans, but no such selection is available to choose.
So, how do you create maintenance plans in SQL Server 2005 Express Edition?
Thanks!
childofthe1980sExpress doesn't come with SQL Agent. Have a look at these:
http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
Backing up Express
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part II
http://www.sqldbatips.com/showarticle.asp?ID=29
--
Andrew J. Kelly SQL MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:2FC46958-D2C0-4120-B6C1-583FCE607044@.microsoft.com...
> Hello:
> I know how to create database maintenance plans (automated backups) in SQL
> Server 2000 and 2005.
> But, I have never done so in SQL Server 2005 Express Edition.
> I tried right-clicking on maintenance plans in 2005 Express so that I
> could
> choose to create new plans, but no such selection is available to choose.
> So, how do you create maintenance plans in SQL Server 2005 Express
> Edition?
> Thanks!
> childofthe1980s

Database Maintenance Plans and shrink database

I have read that having databases auto shrink can cause performance
problems, timeouts and fragmentation. I was wondering if using the "Remove
unused space from database files" from the Optimizations tab in Database
Maintenance Plans had the same affect. Should I avaoid using those two
settings?
Thanks
Yes (although maintenance plans are usually scheduled out of core business
hours). Have a look at http://www.karaszi.com/sqlserver/info_dont_shrink.asp
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Alison Blackburn" <alison.blackburn@.thalerus.com> wrote in message
news:Ohn3boEFFHA.2756@.TK2MSFTNGP15.phx.gbl...
>I have read that having databases auto shrink can cause performance
>problems, timeouts and fragmentation. I was wondering if using the "Remove
>unused space from database files" from the Optimizations tab in Database
>Maintenance Plans had the same affect. Should I avaoid using those two
>settings?
> Thanks
>

Database Maintenance Plans and shrink database

I have read that having databases auto shrink can cause performance
problems, timeouts and fragmentation. I was wondering if using the "Remove
unused space from database files" from the Optimizations tab in Database
Maintenance Plans had the same affect. Should I avaoid using those two
settings?
ThanksYes (although maintenance plans are usually scheduled out of core business
hours). Have a look at http://www.karaszi.com/sqlserver/info_dont_shrink.asp
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Alison Blackburn" <alison.blackburn@.thalerus.com> wrote in message
news:Ohn3boEFFHA.2756@.TK2MSFTNGP15.phx.gbl...
>I have read that having databases auto shrink can cause performance
>problems, timeouts and fragmentation. I was wondering if using the "Remove
>unused space from database files" from the Optimizations tab in Database
>Maintenance Plans had the same affect. Should I avaoid using those two
>settings?
> Thanks
>

Database Maintenance Plans and shrink database

I have read that having databases auto shrink can cause performance
problems, timeouts and fragmentation. I was wondering if using the "Remove
unused space from database files" from the Optimizations tab in Database
Maintenance Plans had the same affect. Should I avaoid using those two
settings?
ThanksYes (although maintenance plans are usually scheduled out of core business
hours). Have a look at http://www.karaszi.com/sqlserver/info_dont_shrink.asp
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Alison Blackburn" <alison.blackburn@.thalerus.com> wrote in message
news:Ohn3boEFFHA.2756@.TK2MSFTNGP15.phx.gbl...
>I have read that having databases auto shrink can cause performance
>problems, timeouts and fragmentation. I was wondering if using the "Remove
>unused space from database files" from the Optimizations tab in Database
>Maintenance Plans had the same affect. Should I avaoid using those two
>settings?
> Thanks
>

Database Maintenance Plans - query?

Is there an easier way to get a listing of all your
maintenance plans, what they do, and when they are
scheduled to occur - in a multiserver environment - aside
from pulling up enterprise manager for each server and
writing it all down? I would think these would be defined
in the system information and I could query it out but I
can't find anything about it in BOL or in searching KB and
newsgroups. Help please?
Thanks,
Kevin
Just one of the many problems with maintenance plans is that some of the
data is stored in the MP system tables, some is stored in Job system tables
and some is actually parsed from the command strings in the job steps. Here
is a query to list all jobs with their schedules, descriptions etc. You
could expand it a bit to join with the MP system tables to get just the ones
associated with the MP's.
Maintenance Plan system tables
sysdbmaintplan_databases
sysdbmaintplan_history
sysdbmaintplan_jobs
sysdbmaintplans
select a.[Name],a.[Enabled] AS [J_E],
b.[Enabled] AS [S_E],
case b.freq_type
when 1 then 'Run Once'
when 4 then 'Runs Daily'
when 8 then 'Every Week'
+ case freq_interval & 2 when 2 then ' on Mondays' else '' end
+ case freq_interval & 4 when 4 then ' on Tuesday' else '' end
+ case freq_interval & 8 when 8 then ' on Wednesday' else '' end
+ case freq_interval & 16 when 16 then ' on Thursday' else '' end
+ case freq_interval & 32 when 32 then ' on Friday' else '' end
+ case freq_interval & 64 when 64 then ' on Saturday' else '' end
+ case freq_interval & 1 when 1 then ' on Sunday' else '' end
when 16 then 'Mthly on day ' + convert(varchar(2), freq_interval)
when 32 then 'Mthly ' + case freq_relative_interval
when 1 then 'Every First '
when 2 then 'Every Second '
when 4 then 'Every Third '
when 8 then 'Every Fourth '
when 16 then 'Every Last '
end
+ case b.freq_interval
when 1 then ' on Monday'
when 2 then ' on Tuesdsay'
when 3 then ' on Wednesday'
when 4 then ' on Thursday'
when 5 then ' on Friday'
when 6 then ' on Saturday'
when 7 then ' on Sunday'
when 8 then 'Day'
when 9 then 'Week day'
when 10 then 'Weekend day'
end
when 64 then 'Startup'
when 128 then 'Idle'
else 'Err'
end as schedule,
case b.freq_subday_type
when 1 then 'Runs at:'
when 2 then 'every ' + convert(varchar(3), freq_subday_interval) + '
seconds'
when 4 then 'every ' + convert(varchar(3), freq_subday_interval) + '
minutes'
when 8 then 'every ' + convert(varchar(3), freq_subday_interval) + '
hours'
end as frequency,
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time), 6), 1, 2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time), 6) ,3 ,2) + ':'+
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time),6) ,5 ,2)
as start_at,
case freq_subday_type
when 1 then NULL
else
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_end_time), 6), 1, 2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6), active_end_time),6) ,3 ,2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6), active_end_time),6) ,5 ,2)
end as end_at,
a.[Description]
from [msdb].[dbo].[sysjobs] AS a INNER JOIN [msdb].[dbo].[sysjobschedules]
AS b
ON a.[Job_ID] = b.[Job_ID]
ORDER BY a.[Name]

Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:12ecb01c44355$738f2a60$a001280a@.phx.gbl...
> Is there an easier way to get a listing of all your
> maintenance plans, what they do, and when they are
> scheduled to occur - in a multiserver environment - aside
> from pulling up enterprise manager for each server and
> writing it all down? I would think these would be defined
> in the system information and I could query it out but I
> can't find anything about it in BOL or in searching KB and
> newsgroups. Help please?
> Thanks,
> Kevin

Database Maintenance Plans - query?

Is there an easier way to get a listing of all your
maintenance plans, what they do, and when they are
scheduled to occur - in a multiserver environment - aside
from pulling up enterprise manager for each server and
writing it all down? I would think these would be defined
in the system information and I could query it out but I
can't find anything about it in BOL or in searching KB and
newsgroups. Help please?
Thanks,
KevinJust one of the many problems with maintenance plans is that some of the
data is stored in the MP system tables, some is stored in Job system tables
and some is actually parsed from the command strings in the job steps. Here
is a query to list all jobs with their schedules, descriptions etc. You
could expand it a bit to join with the MP system tables to get just the ones
associated with the MP's.
Maintenance Plan system tables
--
sysdbmaintplan_databases
sysdbmaintplan_history
sysdbmaintplan_jobs
sysdbmaintplans
select a.[Name],a.[Enabled] AS [J_E],
b.[Enabled] AS [S_E],
case b.freq_type
when 1 then 'Run Once'
when 4 then 'Runs Daily'
when 8 then 'Every Week'
+ case freq_interval & 2 when 2 then ' on Mondays' else '' end
+ case freq_interval & 4 when 4 then ' on Tuesday' else '' end
+ case freq_interval & 8 when 8 then ' on Wednesday' else '' end
+ case freq_interval & 16 when 16 then ' on Thursday' else '' end
+ case freq_interval & 32 when 32 then ' on Friday' else '' end
+ case freq_interval & 64 when 64 then ' on Saturday' else '' end
+ case freq_interval & 1 when 1 then ' on Sunday' else '' end
when 16 then 'Mthly on day ' + convert(varchar(2), freq_interval)
when 32 then 'Mthly ' + case freq_relative_interval
when 1 then 'Every First '
when 2 then 'Every Second '
when 4 then 'Every Third '
when 8 then 'Every Fourth '
when 16 then 'Every Last '
end
+ case b.freq_interval
when 1 then ' on Monday'
when 2 then ' on Tuesdsay'
when 3 then ' on Wednesday'
when 4 then ' on Thursday'
when 5 then ' on Friday'
when 6 then ' on Saturday'
when 7 then ' on Sunday'
when 8 then 'Day'
when 9 then 'Week day'
when 10 then 'Weekend day'
end
when 64 then 'Startup'
when 128 then 'Idle'
else 'Err'
end as schedule,
case b.freq_subday_type
when 1 then 'Runs at:'
when 2 then 'every ' + convert(varchar(3), freq_subday_interval) + '
seconds'
when 4 then 'every ' + convert(varchar(3), freq_subday_interval) + '
minutes'
when 8 then 'every ' + convert(varchar(3), freq_subday_interval) + '
hours'
end as frequency,
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time), 6), 1, 2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time), 6) ,3 ,2) + ':'+
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time),6)
,5 ,2)
as start_at,
case freq_subday_type
when 1 then NULL
else
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_end_time), 6), 1, 2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6), active_end_time),6) ,3 ,2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6), active_end_time),6) ,5 ,2)
end as end_at,
a.[Description]
from [msdb].[dbo].[sysjobs] AS a INNER JOIN [msdb].[dbo]
.[sysjobschedules]
AS b
ON a.[Job_ID] = b.[Job_ID]
ORDER BY a.[Name]
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:12ecb01c44355$738f2a60$a001280a@.phx
.gbl...
> Is there an easier way to get a listing of all your
> maintenance plans, what they do, and when they are
> scheduled to occur - in a multiserver environment - aside
> from pulling up enterprise manager for each server and
> writing it all down? I would think these would be defined
> in the system information and I could query it out but I
> can't find anything about it in BOL or in searching KB and
> newsgroups. Help please?
> Thanks,
> Kevin

Database Maintenance Plans - query?

Is there an easier way to get a listing of all your
maintenance plans, what they do, and when they are
scheduled to occur - in a multiserver environment - aside
from pulling up enterprise manager for each server and
writing it all down? I would think these would be defined
in the system information and I could query it out but I
can't find anything about it in BOL or in searching KB and
newsgroups. Help please?
Thanks,
KevinJust one of the many problems with maintenance plans is that some of the
data is stored in the MP system tables, some is stored in Job system tables
and some is actually parsed from the command strings in the job steps. Here
is a query to list all jobs with their schedules, descriptions etc. You
could expand it a bit to join with the MP system tables to get just the ones
associated with the MP's.
Maintenance Plan system tables
--
sysdbmaintplan_databases
sysdbmaintplan_history
sysdbmaintplan_jobs
sysdbmaintplans
select a.[Name],a.[Enabled] AS [J_E],
b.[Enabled] AS [S_E],
case b.freq_type
when 1 then 'Run Once'
when 4 then 'Runs Daily'
when 8 then 'Every Week'
+ case freq_interval & 2 when 2 then ' on Mondays' else '' end
+ case freq_interval & 4 when 4 then ' on Tuesday' else '' end
+ case freq_interval & 8 when 8 then ' on Wednesday' else '' end
+ case freq_interval & 16 when 16 then ' on Thursday' else '' end
+ case freq_interval & 32 when 32 then ' on Friday' else '' end
+ case freq_interval & 64 when 64 then ' on Saturday' else '' end
+ case freq_interval & 1 when 1 then ' on Sunday' else '' end
when 16 then 'Mthly on day ' + convert(varchar(2), freq_interval)
when 32 then 'Mthly ' + case freq_relative_interval
when 1 then 'Every First '
when 2 then 'Every Second '
when 4 then 'Every Third '
when 8 then 'Every Fourth '
when 16 then 'Every Last '
end
+ case b.freq_interval
when 1 then ' on Monday'
when 2 then ' on Tuesdsay'
when 3 then ' on Wednesday'
when 4 then ' on Thursday'
when 5 then ' on Friday'
when 6 then ' on Saturday'
when 7 then ' on Sunday'
when 8 then 'Day'
when 9 then 'Week day'
when 10 then 'Weekend day'
end
when 64 then 'Startup'
when 128 then 'Idle'
else 'Err'
end as schedule,
case b.freq_subday_type
when 1 then 'Runs at:'
when 2 then 'every ' + convert(varchar(3), freq_subday_interval) + '
seconds'
when 4 then 'every ' + convert(varchar(3), freq_subday_interval) + '
minutes'
when 8 then 'every ' + convert(varchar(3), freq_subday_interval) + '
hours'
end as frequency,
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time), 6), 1, 2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time), 6) ,3 ,2) + ':'+
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_start_time),6) ,5 ,2)
as start_at,
case freq_subday_type
when 1 then NULL
else
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6),active_end_time), 6), 1, 2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6), active_end_time),6) ,3 ,2) + ':' +
substring(right(stuff(' ', 1, 1, '000000') +
convert(varchar(6), active_end_time),6) ,5 ,2)
end as end_at,
a.[Description]
from [msdb].[dbo].[sysjobs] AS a INNER JOIN [msdb].[dbo].[sysjobschedules]
AS b
ON a.[Job_ID] = b.[Job_ID]
ORDER BY a.[Name]
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:12ecb01c44355$738f2a60$a001280a@.phx.gbl...
> Is there an easier way to get a listing of all your
> maintenance plans, what they do, and when they are
> scheduled to occur - in a multiserver environment - aside
> from pulling up enterprise manager for each server and
> writing it all down? I would think these would be defined
> in the system information and I could query it out but I
> can't find anything about it in BOL or in searching KB and
> newsgroups. Help please?
> Thanks,
> Kevin

Database Maintenance Plans - Not removing Files Older than x days

I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
database on the server and have created a database maintenance plan that
backups up all the database nightly. I have also configured the maintenance
plan to delete back files older than 3 days old but this isn't currently
happening.
I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
seen this problem first. Or if anyone can confirm SP4 fixes this issue.
You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
SP4 on another system to make sure your apps work correctly first, of course.
Have you checked the various logs SQL Server uses? There's a SQL Server Log,
a SQL Server Agent Log, and the Windows Application Event Log. They might
point out what is happening.
That being said, there is an extended stored procedure that Microsoft uses
to delete the files. If the Agent service doesn't have the proper rights to
the subdirectory you might find that to be the issue.
"Gary S" wrote:

> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenance
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
>
|||What is the extended store procedure that's used so that I can check it
hasn't been removed.
"Buck Woody - Microsoft SQL Server Team" wrote:
[vbcol=seagreen]
> You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
> SP4 on another system to make sure your apps work correctly first, of course.
> Have you checked the various logs SQL Server uses? There's a SQL Server Log,
> a SQL Server Agent Log, and the Windows Application Event Log. They might
> point out what is happening.
> That being said, there is an extended stored procedure that Microsoft uses
> to delete the files. If the Agent service doesn't have the proper rights to
> the subdirectory you might find that to be the issue.
> "Gary S" wrote:
|||It's sp_delete_file - and it's undocumented, meaning unsupported for direct
use by users. Check this thread:
https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
"Gary S" wrote:
[vbcol=seagreen]
> What is the extended store procedure that's used so that I can check it
> hasn't been removed.
> "Buck Woody - Microsoft SQL Server Team" wrote:
|||Slight correction - that's XP_delete_file. Had an S in there!
"Buck Woody - Microsoft SQL Server Team" wrote:
[vbcol=seagreen]
> It's sp_delete_file - and it's undocumented, meaning unsupported for direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
|||On Feb 14, 8:35 am, Gary S <G...@.discussions.microsoft.com> wrote:
> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenance
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
There are a couple of common causes for this:
1. The maintenance plan is configured to do transaction log backups,
but one of the databases included is in Simple mode. The plan fails
when it hits this database, and never reaches the "cleanup" step.
2. One of the files to be deleted is "in use" by another process,
such as a tape backup, causing the cleanup process to fail.
Right-click on the maintenance plan itself (not the Agent job), look
at the history, you should be able to get an actual error message from
there.
|||You have to be a sysadmin to run this stored proc, even in SP2 CTP. I have
been told a fix will be raised for a later service pack.
Chris
"Buck Woody - Microsoft SQL Server Team"
<BuckWoodyMicrosoftSQLServerTeam@.discussions.micro soft.com> wrote in message
news:0751636B-0F16-40EA-BAE8-8ADE57217570@.microsoft.com...[vbcol=seagreen]
> It's sp_delete_file - and it's undocumented, meaning unsupported for
> direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
|||Thanks Tracey a number of the database were set to Simple Recovery. I'm not a
big fan of database mainatenance plans (perfer setting up the jobs
individual) so as I'm not 100% certain why the databases are set to simple
I'll create seperate backup jobs.
"Tracy McKibben" wrote:

> On Feb 14, 8:35 am, Gary S <G...@.discussions.microsoft.com> wrote:
> There are a couple of common causes for this:
> 1. The maintenance plan is configured to do transaction log backups,
> but one of the databases included is in Simple mode. The plan fails
> when it hits this database, and never reaches the "cleanup" step.
> 2. One of the files to be deleted is "in use" by another process,
> such as a tape backup, causing the cleanup process to fail.
> Right-click on the maintenance plan itself (not the Agent job), look
> at the history, you should be able to get an actual error message from
> there.
>
|||On Feb 15, 5:13 am, Gary S <G...@.discussions.microsoft.com> wrote:
> Thanks Tracey a number of the database were set to Simple Recovery. I'm not a
> big fan of database mainatenance plans (perfer setting up the jobs
> individual) so as I'm not 100% certain why the databases are set to simple
> I'll create seperate backup jobs.
>
Here's a script of mine that might help you out:
http://realsqlguy.blogspot.com/2007/02/automating-database-backups.html

Database Maintenance Plans - Not removing Files Older than x days

I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
database on the server and have created a database maintenance plan that
backups up all the database nightly. I have also configured the maintenance
plan to delete back files older than 3 days old but this isn't currently
happening.
I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
seen this problem first. Or if anyone can confirm SP4 fixes this issue.You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
SP4 on another system to make sure your apps work correctly first, of course.
Have you checked the various logs SQL Server uses? There's a SQL Server Log,
a SQL Server Agent Log, and the Windows Application Event Log. They might
point out what is happening.
That being said, there is an extended stored procedure that Microsoft uses
to delete the files. If the Agent service doesn't have the proper rights to
the subdirectory you might find that to be the issue.
"Gary S" wrote:
> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenance
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
>|||What is the extended store procedure that's used so that I can check it
hasn't been removed.
"Buck Woody - Microsoft SQL Server Team" wrote:
> You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
> SP4 on another system to make sure your apps work correctly first, of course.
> Have you checked the various logs SQL Server uses? There's a SQL Server Log,
> a SQL Server Agent Log, and the Windows Application Event Log. They might
> point out what is happening.
> That being said, there is an extended stored procedure that Microsoft uses
> to delete the files. If the Agent service doesn't have the proper rights to
> the subdirectory you might find that to be the issue.
> "Gary S" wrote:
> > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > database on the server and have created a database maintenance plan that
> > backups up all the database nightly. I have also configured the maintenance
> > plan to delete back files older than 3 days old but this isn't currently
> > happening.
> >
> > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> >
> >|||It's sp_delete_file - and it's undocumented, meaning unsupported for direct
use by users. Check this thread:
https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
"Gary S" wrote:
> What is the extended store procedure that's used so that I can check it
> hasn't been removed.
> "Buck Woody - Microsoft SQL Server Team" wrote:
> > You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
> > SP4 on another system to make sure your apps work correctly first, of course.
> >
> > Have you checked the various logs SQL Server uses? There's a SQL Server Log,
> > a SQL Server Agent Log, and the Windows Application Event Log. They might
> > point out what is happening.
> >
> > That being said, there is an extended stored procedure that Microsoft uses
> > to delete the files. If the Agent service doesn't have the proper rights to
> > the subdirectory you might find that to be the issue.
> >
> > "Gary S" wrote:
> >
> > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > > database on the server and have created a database maintenance plan that
> > > backups up all the database nightly. I have also configured the maintenance
> > > plan to delete back files older than 3 days old but this isn't currently
> > > happening.
> > >
> > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> > >
> > >|||Slight correction - that's XP_delete_file. Had an S in there!
"Buck Woody - Microsoft SQL Server Team" wrote:
> It's sp_delete_file - and it's undocumented, meaning unsupported for direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
> > What is the extended store procedure that's used so that I can check it
> > hasn't been removed.
> >
> > "Buck Woody - Microsoft SQL Server Team" wrote:
> >
> > > You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
> > > SP4 on another system to make sure your apps work correctly first, of course.
> > >
> > > Have you checked the various logs SQL Server uses? There's a SQL Server Log,
> > > a SQL Server Agent Log, and the Windows Application Event Log. They might
> > > point out what is happening.
> > >
> > > That being said, there is an extended stored procedure that Microsoft uses
> > > to delete the files. If the Agent service doesn't have the proper rights to
> > > the subdirectory you might find that to be the issue.
> > >
> > > "Gary S" wrote:
> > >
> > > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > > > database on the server and have created a database maintenance plan that
> > > > backups up all the database nightly. I have also configured the maintenance
> > > > plan to delete back files older than 3 days old but this isn't currently
> > > > happening.
> > > >
> > > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > > > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> > > >
> > > >|||On Feb 14, 8:35 am, Gary S <G...@.discussions.microsoft.com> wrote:
> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenance
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
There are a couple of common causes for this:
1. The maintenance plan is configured to do transaction log backups,
but one of the databases included is in Simple mode. The plan fails
when it hits this database, and never reaches the "cleanup" step.
2. One of the files to be deleted is "in use" by another process,
such as a tape backup, causing the cleanup process to fail.
Right-click on the maintenance plan itself (not the Agent job), look
at the history, you should be able to get an actual error message from
there.|||You have to be a sysadmin to run this stored proc, even in SP2 CTP. I have
been told a fix will be raised for a later service pack.
Chris
"Buck Woody - Microsoft SQL Server Team"
<BuckWoodyMicrosoftSQLServerTeam@.discussions.microsoft.com> wrote in message
news:0751636B-0F16-40EA-BAE8-8ADE57217570@.microsoft.com...
> It's sp_delete_file - and it's undocumented, meaning unsupported for
> direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
>> What is the extended store procedure that's used so that I can check it
>> hasn't been removed.
>> "Buck Woody - Microsoft SQL Server Team" wrote:
>> > You'll want to apply SP4 anyway, for lots of other reasons. Test the
>> > setup of
>> > SP4 on another system to make sure your apps work correctly first, of
>> > course.
>> >
>> > Have you checked the various logs SQL Server uses? There's a SQL Server
>> > Log,
>> > a SQL Server Agent Log, and the Windows Application Event Log. They
>> > might
>> > point out what is happening.
>> >
>> > That being said, there is an extended stored procedure that Microsoft
>> > uses
>> > to delete the files. If the Agent service doesn't have the proper
>> > rights to
>> > the subdirectory you might find that to be the issue.
>> >
>> > "Gary S" wrote:
>> >
>> > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a
>> > > number of
>> > > database on the server and have created a database maintenance plan
>> > > that
>> > > backups up all the database nightly. I have also configured the
>> > > maintenance
>> > > plan to delete back files older than 3 days old but this isn't
>> > > currently
>> > > happening.
>> > >
>> > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone
>> > > else has
>> > > seen this problem first. Or if anyone can confirm SP4 fixes this
>> > > issue.
>> > >
>> > >|||> It's sp_delete_file - and it's undocumented, meaning unsupported for direct
> use by users.
Buck,
Above is for 2005. For 2000, the files are removed by sqlmaint.exe (which is called by xp_sqlmaint
if the plan is created by the wizard).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Buck Woody - Microsoft SQL Server Team" <BuckWoodyMicrosoftSQLServerTeam@.discussions.microsoft.com>
wrote in message news:0751636B-0F16-40EA-BAE8-8ADE57217570@.microsoft.com...
> It's sp_delete_file - and it's undocumented, meaning unsupported for direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
>> What is the extended store procedure that's used so that I can check it
>> hasn't been removed.
>> "Buck Woody - Microsoft SQL Server Team" wrote:
>> > You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
>> > SP4 on another system to make sure your apps work correctly first, of course.
>> >
>> > Have you checked the various logs SQL Server uses? There's a SQL Server Log,
>> > a SQL Server Agent Log, and the Windows Application Event Log. They might
>> > point out what is happening.
>> >
>> > That being said, there is an extended stored procedure that Microsoft uses
>> > to delete the files. If the Agent service doesn't have the proper rights to
>> > the subdirectory you might find that to be the issue.
>> >
>> > "Gary S" wrote:
>> >
>> > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
>> > > database on the server and have created a database maintenance plan that
>> > > backups up all the database nightly. I have also configured the maintenance
>> > > plan to delete back files older than 3 days old but this isn't currently
>> > > happening.
>> > >
>> > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
>> > > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
>> > >
>> > >|||Thanks Tracey a number of the database were set to Simple Recovery. I'm not a
big fan of database mainatenance plans (perfer setting up the jobs
individual) so as I'm not 100% certain why the databases are set to simple
I'll create seperate backup jobs.
"Tracy McKibben" wrote:
> On Feb 14, 8:35 am, Gary S <G...@.discussions.microsoft.com> wrote:
> > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > database on the server and have created a database maintenance plan that
> > backups up all the database nightly. I have also configured the maintenance
> > plan to delete back files older than 3 days old but this isn't currently
> > happening.
> >
> > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> There are a couple of common causes for this:
> 1. The maintenance plan is configured to do transaction log backups,
> but one of the databases included is in Simple mode. The plan fails
> when it hits this database, and never reaches the "cleanup" step.
> 2. One of the files to be deleted is "in use" by another process,
> such as a tape backup, causing the cleanup process to fail.
> Right-click on the maintenance plan itself (not the Agent job), look
> at the history, you should be able to get an actual error message from
> there.
>|||On Feb 15, 5:13 am, Gary S <G...@.discussions.microsoft.com> wrote:
> Thanks Tracey a number of the database were set to Simple Recovery. I'm not a
> big fan of database mainatenance plans (perfer setting up the jobs
> individual) so as I'm not 100% certain why the databases are set to simple
> I'll create seperate backup jobs.
>
Here's a script of mine that might help you out:
http://realsqlguy.blogspot.com/2007/02/automating-database-backups.html

Database Maintenance Plans - Not removing Files Older than x days

I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number o
f
database on the server and have created a database maintenance plan that
backups up all the database nightly. I have also configured the maintenance
plan to delete back files older than 3 days old but this isn't currently
happening.
I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
seen this problem first. Or if anyone can confirm SP4 fixes this issue.You'll want to apply SP4 anyway, for lots of other reasons. Test the setup o
f
SP4 on another system to make sure your apps work correctly first, of course
.
Have you checked the various logs SQL Server uses? There's a SQL Server Log,
a SQL Server Agent Log, and the Windows Application Event Log. They might
point out what is happening.
That being said, there is an extended stored procedure that Microsoft uses
to delete the files. If the Agent service doesn't have the proper rights to
the subdirectory you might find that to be the issue.
"Gary S" wrote:

> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number
of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenanc
e
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else h
as
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
>|||On Feb 14, 8:35 am, Gary S <G...@.discussions.microsoft.com> wrote:
> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number
of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenanc
e
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else h
as
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
There are a couple of common causes for this:
1. The maintenance plan is configured to do transaction log backups,
but one of the databases included is in Simple mode. The plan fails
when it hits this database, and never reaches the "cleanup" step.
2. One of the files to be deleted is "in use" by another process,
such as a tape backup, causing the cleanup process to fail.
Right-click on the maintenance plan itself (not the Agent job), look
at the history, you should be able to get an actual error message from
there.

Database Maintenance Plans

Hello everyone,
I'm new to DB Maint Plans, so let me apologize upfront. I've taken over a system from a DBA who is no longer working here, and he set up Maint Plans for all of the existing DBs. The plans show up in the Enterprise Manager under "Management->Database Maintenance Plans" like they should, but there are also entries in the "Management->SQL Server Agent->Jobs" area. When I set up a new DB Maint Plan for a new DB, it seems to be working fine, but I don't have any corresponding entries in Jobs. Did the other DBA set these up manually? Does anyone know why he might have done this? Is it needed? The jobs and job steps look like the following:

[DBName]Full:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID 33C423D0-CC31-40BD-A357-7DCCAB1DC262 -WriteHistory -VrfyBackup -BkUpMedia DISK -BkUpDB "W:\sqldata\MSSQL$P001\Backup" -DelBkUps 1WEEKS -CrBkSubDir -BkExt "BAK"'

[DBName]Maint Integrity Checks:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID 33C423D0-CC31-40BD-A357-7DCCAB1DC262 -WriteHistory -CkDB '

[DBName]Maint Optimizations:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID 33C423D0-CC31-40BD-A357-7DCCAB1DC262 -WriteHistory -RebldIdx 10 -RmUnusedSpace 50 10 '

Any help or insight would be greatly appreciated!
Thanks in advance,
CatWhen you set up a plan, it should set up a job. In Enterprise Manager folders window, right-click on Jobs and select "Refresh". I'm betting the GUI just isn't aware of the change you made...|||I would suggest that you start with BOL (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/entrmgr/em_6x7w.asp) for Database Maintenance Plans, and go from there.

-PatP|||When you set up a plan, it should set up a job. In Enterprise Manager folders window, right-click on Jobs and select "Refresh". I'm betting the GUI just isn't aware of the change you made...

Hi Blindman,
Thanks for your reply. I refreshed the GUI for Jobs, but I still don't see my maint plan tasks. Strange! I figured that it must have set up the jobs automatically, but since it didn't set up anything for mine, I didn't know what to think. Do you know if I might have done something incorrectly in setting up my plan? They appear to be working fine.

Well, any further insight would be appreciated.
Thanks for your time.
Cat|||Sorry. I'm not sure why they aren't showing up in your job list. I don't use the Maintenance Plans anyway.|||I would suggest that you start with BOL (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/entrmgr/em_6x7w.asp) for Database Maintenance Plans, and go from there.

-PatP

I have looked there (if I hadn't I would not have been able to set up a plan in the first place). If I had found the answers to my specific questions, I would not have posted them here. I realize that there are a lot of people who post questions on these boards without taking any time to research the answers themselves, but... 1) I am not one of them, and 2) Sometimes it is easier and less frustrating to ask a human for a quick answer to a question than to try and weed through the enormous amount of information contained in the BOL. If you are going to take the time to respond to a post, it would be more helpful if you would offer more specific areas or keywords to search on to reduce the amount of time spent pouring over information that does not apply.

Thank you for your time.
Cat|||Sorry. I'm not sure why they aren't showing up in your job list. I don't use the Maintenance Plans anyway.

Well, thank you! At least I know that the previous DBA did not manually set up the jobs. That's one mystery solved.

Thanks again, you're a sweetheart!
Cat|||Not necessarily. I set up jobs manually. The Maintenance Plan wizard sucks.|||I have If you are going to take the time to respond to a post, it would be more helpful if you would offer more specific areas or keywords to search on to reduce the amount of time spent pouring over information that does not apply.

Thank you for your time.
Cat
Hi Cat,
I think you have meet with some of the best and wonderful people of this forum.They are gurus in this field and they spend their valuable and busy time to answer questions from the most difficult one to the most silliest one.I bet that their suggestions are most helpful and have a deep insight.They have a huge patience and delicate word style to deal with everybody with extreme politeness.I suggest you to follow them without any hesitation,bcoz they have the best intention that you could think of. I am saying this not only they are my favourite but they are really a nice human being.|||Well, I'm not always delicate... ;)|||As Blindman noted, the Maintenance Plan Wizard is better than nothing, but to a DBA that's been around for a while it isn't a lot better than nothing. I'm one of the "crusty old pharts" that still prefers the level of control that comes from writing the maintenance scripts myself at the Transact-SQL level.

Usually when I see what you've decribed (Maintenance plans set up, then jobs set up to further customize the plan), it usually means that whoever set them up originally figured out they needed more, so they manually scheduled the job to allow them to customize the existing setup using parameters.

Sorry if I was a bit short up front. I've been running into a lot of posters/users complaining something to the effect of: "My toy is broke, you need to fix it for me, NOW" and that apparently carried forward into my response to your original question. I should have read it more closely before I responded.

-PatP|||Delicately handled, Pat.|||Sorry if I was a bit short up front. I've been running into a lot of posters/users complaining something to the effect of: "My toy is broke, you need to fix it for me, NOW" and that apparently carried forward into my response to your original question. I should have read it more closely before I responded.

-PatP

Thank you for that! And I'm sorry too if my tone was a bit harsh, I had been having a frustrating day. I have seen many of the posts on this board which you describe and I know that it can be frustrating.

I suspect that the previous DBA either did not set up the jobs himself and they were set up by SQL Server (like blindman suggested), OR he did set them up but only because he thought he had to rather than because he wanted to tweek them. I have come to find many of his DBA practises quite suspect to say the least.

Thanks again to everyone for their responses!
Cat

Database Maintenance Plans

Setting up SQL Server Maintenance Plans. Getting the following error set on
some tasks:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft][ODBC SQL
Server Driver][SQL Server]Database state cannot be changed while other users
are using the database 'abcdefg'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[4] Database abcdefg: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC SQL
Server Driver][SQL Server]Repair statement not processed. Database needs to
be in single user mode.
-----
As a result, I'm assuming the job must disconnect everyone first, except the
job itself. The only way I can find to do this is to issue a DISCONNECT ALL
statement. This is new turf for me, having never been a DBA. Therefore,
please give me any other options or feedback.
Thanks :-)
You can try modifying the job for the maintenance plan and adding a step to
do the following:
ALTER DATABASE <name> SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE.
Let us know if it helps.
-Argenis
"Brett Ossman" <BrettOssman@.discussions.microsoft.com> wrote in message
news:A2B4D992-8FB9-4F7C-A559-EB6FDCA32D66@.microsoft.com...
> Setting up SQL Server Maintenance Plans. Getting the following error set
on
> some tasks:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Database state cannot be changed while other
users
> are using the database 'abcdefg'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
> failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
> [4] Database abcdefg: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Repair statement not processed. Database needs
to
> be in single user mode.
> ----
--
> As a result, I'm assuming the job must disconnect everyone first, except
the
> job itself. The only way I can find to do this is to issue a DISCONNECT
ALL
> statement. This is new turf for me, having never been a DBA. Therefore,
> please give me any other options or feedback.
> Thanks :-)
>
|||Actually the job is attempting to ALTER DATABASE:
[vbcol=seagreen]
so I'm guessing it cannot because there are open connections.
Thanks anyway
"Argenis Fernandez" wrote:

> You can try modifying the job for the maintenance plan and adding a step to
> do the following:
> ALTER DATABASE <name> SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE.
> Let us know if it helps.
> -Argenis
>
> "Brett Ossman" <BrettOssman@.discussions.microsoft.com> wrote in message
> news:A2B4D992-8FB9-4F7C-A559-EB6FDCA32D66@.microsoft.com...
> on
> SQL
> users
> SQL
> to
> --
> the
> ALL
>
>
|||Yes, but probably the job is not issuing a "WITH ROLLBACK IMMEDIATE"
statement. Can't tell for sure. You might want to give it a try -- just
remember to bring the DB to MULTI_USER again at the end of the job.
-Argenis
"Brett Ossman" <BrettOssman@.discussions.microsoft.com> wrote in message
news:DB23A1EC-B4EF-469C-BCD9-DAF6466FFF45@.microsoft.com...[vbcol=seagreen]
> Actually the job is attempting to ALTER DATABASE:
statement[vbcol=seagreen]
> so I'm guessing it cannot because there are open connections.
> Thanks anyway
>
> "Argenis Fernandez" wrote:
to[vbcol=seagreen]
set[vbcol=seagreen]
[Microsoft][ODBC[vbcol=seagreen]
statement[vbcol=seagreen]
failed.[vbcol=seagreen]
[Microsoft][ODBC[vbcol=seagreen]
needs[vbcol=seagreen]
> ----
except[vbcol=seagreen]
DISCONNECT[vbcol=seagreen]
Therefore,[vbcol=seagreen]
|||Uncheck the "attempt to repair minor problems" option in your maint plan. If you have a corruption,
you'd want to know about it and do root cause analysis instead of "having someone trying to fix it
overnight".
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Brett Ossman" <BrettOssman@.discussions.microsoft.com> wrote in message
news:A2B4D992-8FB9-4F7C-A559-EB6FDCA32D66@.microsoft.com...
> Setting up SQL Server Maintenance Plans. Getting the following error set on
> some tasks:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Database state cannot be changed while other users
> are using the database 'abcdefg'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
> failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
> [4] Database abcdefg: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Repair statement not processed. Database needs to
> be in single user mode.
> -----
> As a result, I'm assuming the job must disconnect everyone first, except the
> job itself. The only way I can find to do this is to issue a DISCONNECT ALL
> statement. This is new turf for me, having never been a DBA. Therefore,
> please give me any other options or feedback.
> Thanks :-)
>

Database Maintenance Plans

Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default...b;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
Harry
Have you verified that the SQL Server Agent is running?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081056070.1087@.pastpower.ne t...
Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default...b;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
Harry
|||Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Have you verified that the SQL Server Agent is running?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.ne t...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default...b;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>
|||Do you have any entries in the SQL Server or SQL Agent error logs - or the
Windows event logs?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081204240.1323@.pastpower.ne t...
Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Have you verified that the SQL Server Agent is running?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.ne t...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default...b;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>
|||There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.ne t...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>
>
|||Right click on SQL Server Agent in EM. Click on Display Error Log. I the
drop-down, select All Types. See if anything pops out.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081307240.1373@.pastpower.ne t...
There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:
[vbcol=seagreen]
> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.ne t...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
(Error
>
|||Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:

> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.ne t...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
> (Error
>
|||What did the warning say?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081409270.1410@.pastpower.ne t...
Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:
[vbcol=seagreen]
> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.ne t...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
the[vbcol=seagreen]
1).[vbcol=seagreen]
> (Error
Opened
>
|||[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:

> What did the warning say?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.ne t...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
> the
> 1).
> Opened
>
|||Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
narrow down the scope of the problem.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081433390.1425@.pastpower.ne t...
[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:
[vbcol=seagreen]
> What did the warning say?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.ne t...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
the[vbcol=seagreen]
> the
which[vbcol=seagreen]
View[vbcol=seagreen]
> 1).
have
> Opened
>