SQL Database maintenance plan

SQL Database maintenance plan

Post by Steve Foster [SBS MVP » Sat, 29 May 2004 22:29:37

> I have recently setup SBS2003. I am attempteing to setup a scheduled
> database backup throught the Database Maintenance Plan and for some
> reason It bombs. I think there is something simple that I am
> overlooking. Any Ideas?

> Event Type:        Warning
> Event Source:      SQLSERVERAGENT
> Event Category:    Job Engine
> Event ID:  208
> Date:              5/26/2004
> Time:              8:09:00 AM
> User:              N/A
> Computer:  TL0
> Description:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0x6ED3623DF2F29F41B9D5F78CC0F49953) - Status:
> Failed - Invoked on: 2004-05-26 08:09:00 - Message: The job failed.
> Unable to determine if the owner (TL0\Administrator) of job DB Backup
> Job for DB Maintenance Plan 'DB Maintenance Plan1' has server access
> (reason: Could not obtain information about Windows NT group/user
> 'TL0\Administrator'. [SQLSTATE 42000] (Error 8198)).

Have you been working on SQL security lately? Removed the
BUILTIN\Administrators group from the Logins perhaps?

Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.


1. SQL 7.0 Database Maintenance Plan Backup errors

I have set up a SQL 7.0 Database Maintenance Plan for our SMS V2 DB backup.
Have activated integrity and consistency checks as well as Backup.

The backup is scheduled M-F for 1AM and appears to work well except for the
following errors that are produced by SMS_COLLECTION_EVALUATOR just after

Message ID 608
Failed to create index "MachineID_idx" on table "Temp__RES_COLL_SMS00008".

Message ID 2511
SMS Collection Evaluator failed to update the membership of collection

Message ID 620
Microsoft SQL Server reported SQL message 3023, severity 16: Backup,
CHECKALLOC, bulk copy, SELECT INTO, and file manipulation (such as CREATE
FILE) operations on a database must be serialized. Reissue the statement
after the current backup, CHECKALLOC, or file manipulation operation is

Please refer to your SMS documentation, SQL documentation, or the Microsoft
Knowledge Base for further troubleshooting information.

I get the same set of messages for SMS00007.
I have rescheduled the consistency and integrity checks for the weekends
only and have unchecked the backup verification.

Have I missed something? Should I be using the SMS DB Maintenance Tasks?

Jerome Boon
CS Energy

2. Layered provider applicatio on NT

3. SMS 2.0 Database Maintenance Plan

4. FS: Indy 175MHz, Irix 6.2, CDROM,2G,64MB,kyb/mouse

5. The database maintenance stops SQL Executive

6. \p@enumi

7. SQL 7.0 database maintenance command

8. Bell or Buzzer

9. SMS 2 and SQL 7 database maintenance

10. Maintenance Plan

11. Database maintenance

12. Database Maintenance Failing

13. SMS Database Maintenance Tasks Missing