Re: Maintenance Plan Caused System To Hang
- From: "Neil" <nrgins@xxxxxxxxx>
- Date: Wed, 7 Jan 2009 09:38:55 -0600
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
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
The plan I had been running in 7 did the following:
- Check database integrity (include indexes; attempt to repair minor
- 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
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!!
- Prev by Date: Re: Maintenance Plan Caused System To Hang
- Next by Date: SQL Server Management Studio Easy Easy Question
- Previous by thread: Re: Maintenance Plan Caused System To Hang
- Next by thread: SQLCMD and database mirroring