Rebuild Index Failing

The SQL Server 2005 (9.0.2047) 'Rebuild Index' maintenance plan task is
failing.
The text file report is of very little help...
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.2047
Report was generated on "SQLSERVER".
Maintenance Plan: Weekly All DB Maintenance Plan
Duration: 00:00:00
Status: Succeeded.
Details:
The job history doesn't tell much either...
Date3/15/2007 8:00:00 PM
LogJob History (Weekly All DB Maintenance Plan)
Step ID0
ServerSQLSERVER
Job NameWeekly All DB Maintenance Plan
Step Name(Job outcome)
Duration04:25:27
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
The job failed. The Job was invoked by Schedule 99 (Weekly All DB
Maintenance Plan). The last step to run was step 1 (Subplan).
These symptoms are worse on (but not limited to) databases migrated from SQL
2000.
I have discovered running 'DBCC UPDATEUSAGE (DatabaseName)' allows Rebuild
Index to run. But eventually Rebuild Index will fail requiring UPDATEUSAGE
be run again.
Is there any way to get a more verbose (meaningful) task report?
What is causing this?
Is there any harm in running UPDATEUSAGE on a regular basis?
Thanks in advance,
John
John,
SP2 will give you a lot more output but there are known problems with maint
plans and checkdb. See:-
http://sqlblog.com/blogs/tibor_karaszi/archive/2007/03/08/be-aware-sp2-maint-plans-and-checkdb.aspx
Chris
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:5F4C1EBF-EE19-486C-A09C-D6B1F3614108@.microsoft.com...
> The SQL Server 2005 (9.0.2047) 'Rebuild Index' maintenance plan task is
> failing.
> The text file report is of very little help...
> Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.2047
> Report was generated on "SQLSERVER".
> Maintenance Plan: Weekly All DB Maintenance Plan
> Duration: 00:00:00
> Status: Succeeded.
> Details:
> The job history doesn't tell much either...
> Date 3/15/2007 8:00:00 PM
> Log Job History (Weekly All DB Maintenance Plan)
> Step ID 0
> Server SQLSERVER
> Job Name Weekly All DB Maintenance Plan
> Step Name (Job outcome)
> Duration 04:25:27
> Sql Severity 0
> Sql Message ID 0
> Operator Emailed
> Operator Net sent
> Operator Paged
> Retries Attempted 0
> Message
> The job failed. The Job was invoked by Schedule 99 (Weekly All DB
> Maintenance Plan). The last step to run was step 1 (Subplan).
>
> These symptoms are worse on (but not limited to) databases migrated from
> SQL
> 2000.
> I have discovered running 'DBCC UPDATEUSAGE (DatabaseName)' allows Rebuild
> Index to run. But eventually Rebuild Index will fail requiring
> UPDATEUSAGE
> be run again.
> Is there any way to get a more verbose (meaningful) task report?
> What is causing this?
> Is there any harm in running UPDATEUSAGE on a regular basis?
> Thanks in advance,
> John
|||Its well known that index usage counts could get out of whack on SQL 2000
but the algorithm was changed for 2005 suh that they never should. I'd
really like to know more about this - can you send me email with the error
messages you're getting from the rebuilds? (Go to the blog site below and
send email through there).
Thanks
Paul Randal
Principal Lead Program Manager
Microsoft SQL Server Core Storage Engine,
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:5F4C1EBF-EE19-486C-A09C-D6B1F3614108@.microsoft.com...
> The SQL Server 2005 (9.0.2047) 'Rebuild Index' maintenance plan task is
> failing.
> The text file report is of very little help...
> Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.2047
> Report was generated on "SQLSERVER".
> Maintenance Plan: Weekly All DB Maintenance Plan
> Duration: 00:00:00
> Status: Succeeded.
> Details:
> The job history doesn't tell much either...
> Date 3/15/2007 8:00:00 PM
> Log Job History (Weekly All DB Maintenance Plan)
> Step ID 0
> Server SQLSERVER
> Job Name Weekly All DB Maintenance Plan
> Step Name (Job outcome)
> Duration 04:25:27
> Sql Severity 0
> Sql Message ID 0
> Operator Emailed
> Operator Net sent
> Operator Paged
> Retries Attempted 0
> Message
> The job failed. The Job was invoked by Schedule 99 (Weekly All DB
> Maintenance Plan). The last step to run was step 1 (Subplan).
>
> These symptoms are worse on (but not limited to) databases migrated from
> SQL
> 2000.
> I have discovered running 'DBCC UPDATEUSAGE (DatabaseName)' allows Rebuild
> Index to run. But eventually Rebuild Index will fail requiring
> UPDATEUSAGE
> be run again.
> Is there any way to get a more verbose (meaningful) task report?
> What is causing this?
> Is there any harm in running UPDATEUSAGE on a regular basis?
> Thanks in advance,
> John
|||Hi Paul,
Thank you for taking an interest in my little dilemma.
Forgive me but I don't see how to send an email from your blog. Can you
please expand on how to do it?
Thanks,
John
"Paul S. Randal [MS]" wrote:

> Its well known that index usage counts could get out of whack on SQL 2000
> but the algorithm was changed for 2005 suh that they never should. I'd
> really like to know more about this - can you send me email with the error
> messages you're getting from the rebuilds? (Go to the blog site below and
> send email through there).
> Thanks
> --
> Paul Randal
> Principal Lead Program Manager
> Microsoft SQL Server Core Storage Engine,
> http://blogs.msdn.com/sqlserverstorageengine/default.aspx
>
> "John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
> news:5F4C1EBF-EE19-486C-A09C-D6B1F3614108@.microsoft.com...
>
>