Re: Maintenance Plan Caused System To Hang

Here's something to throw out. Both times I did this (ran the maint plan and
ran DBCC CHECKDB) I was connected to the server through Terminal Services.
Even though the server has 2 GB of RAM and is used exclusively for SQL 2005,
perhaps when connected through Terminal Services the memory space is
limited? Just something to throw out there.


"Neil" <nrgins@xxxxxxxxx> wrote in message
news:oVG8l.13441$c45.6965@xxxxxxxxxxxxxxxxxxxxxxx
I recently moved our database from SQL 7 to SQL 2005. I configured the
maintenance plan in SQL 2005 and ran it. However, the server hung when the
plan was run, and had to be rebooted. I'm trying to determine what went
wrong.

The plan I had been running in 7 did the following:

- Check database integrity (include indexes; attempt to repair minor
problems)
- Reorganize data and index pages (change free space percentage to 10%)
- Back up the database and transaction log (verify integrity of each)

The plan I created in 2005, which failed, is as follows:

- Check database integrity (all databases; include indexes)
- Reorganize Indexes (all databases; compact large objects)
- Rebuild indexes (all databases; change free space percentage to 10%)
- Update statistics (all databases; all existing statistics; full scan)
- Back up databases (all databases; full backup; verify backup integrity)

I should note that the database compatibility level had been changed from
7 to 2005 right before the maintenance plan was run. Also, the database
may have been in use by several users.

Looking at the logs at about the time the maintenance plan was run, I see
that it ran CHECKDB on all the system databases and found zero errors. It
then would have gone on to running CHECKDB on my user-created database.
The log shows it called "Password Policy Checking API" with a severity of
"Success Audit," as it had been previously. And then, the last entry in
the log was the following:

"Windows cannot obtain the domain controller name for your computer
network. (An unexpected network error occurred. ). Group Policy processing
aborted."

At that point, the system hung.

So I'm wondering if anyone has any idea what could have caused this error
and the system to hang. Could the fact that a couple of users might have
been in the database at the time affected this?

Also, was wondering if it looks like I created the plan correctly, or if
there are any recommendations for changes to it.

Thanks so much!!

Neil



.

Relevant Pages

  • Re: DBCC CHCECKTABLE faults go away after reboot?
    ... The database with corrupt sysindexes cannot be repaired and will need to be ... documented reasons not to run CHECKDB on a very busy system. ... Microsoft SQL Server Storage Engine ... > - one database with sysindexes table failing DBCC CHECKDB, ...
    (microsoft.public.sqlserver.server)
  • Re: "Attempt to repair any minor problems." What is the point?
    ... The message indicates that the *database* needs to be in single-user mode. ... This should not be confused with the *server* being in single-user mode. ... > What is the point of having this checkbox on the Database Mainenance Plan ... > For SqlAgent to be running, it requires NOT Single User Mode. ...
    (microsoft.public.sqlserver.server)
  • Strategy for a databse
    ... I have some experience with building a database of people, ... regular trips but often also charters of various lenghts. ... I need to plan ... For all these things, and many others I have reports, in Excel format, ...
    (microsoft.public.access.gettingstarted)
  • How Do I Restore A Warm Backup If My Primary Server Fails?
    ... In SQL 2000 I have been using Log Shipping to keep a warm backup copy ... up my Maintenance Plan to implement log shipping, ... same database. ... my secondary server. ...
    (comp.databases.ms-sqlserver)
  • Re: DBCC Checkdb,
    ... Fehler beim Maintenance Plan mit dem ich leider nichts anfangen kann. ... ich habe zur leichteren Fehlerfindung alle weiteren Step disabled - es ... bleibt nur der erste Step Check Databases über. ... The Check Database Integrity task and the Execute T-SQL Statement task in a maintenance plan may lose database context in certain circumstances in SQL Server 2005 builds 3042 through 3053 ...
    (microsoft.public.de.sqlserver)