March 19, 2012 at 5:14 pm
Hello,
I'm the Involuntary DBA around here...On Win2k8 R2 Enterprise running SQL 2k8R2 - I set up a Maintenance Plan to run DBCC CheckDB. Viewing the T-SQL of the Plan shows it did/will run:
USE [master]
GO
DBCC CHECKDB(N'master') WITH NO_INFOMSGS
GO
USE [model]
GO
DBCC CHECKDB(N'model') WITH NO_INFOMSGS
GO
USE [msdb]
GO
DBCC CHECKDB(N'msdb') WITH NO_INFOMSGS
GO
........Same as above for 5 Application Databases
From the ongoing Pefmon monitoring, I show the page file (Page File\%usage) went from zero usage to 100 percent. The page file stayed at 100% until another job ran (2-days later) and locked up the server and forced me to do a reboot. I've never run CheckDB either manually or through a Maintenance Plan prior to this on this database server.
Is this expected / possible? What would be the next steps to find out the cause of this?
Thanks,
Dan Foxley
March 19, 2012 at 9:20 pm
DBCC checkdb is very resource oriented command. The database listed are system databases should not be big problem. Where as the 5 application dbs you never mentioned their sizes. The best way to handle this is to restore the dbs to another dev/staging server and estimate the time taken for the db.
Based on the analysis, you decide what are the dbs can be included in the checkdb at a time.
The DBCC checkdb is nothing but running the below commands on your database.
1) DBCC CHECKALLOC on the database.
2) DBCC CHECKTABLE on every table and view in the database.
3) DBCC CHECKCATALOG on the database.
You can even divide the checkdb into three jobs and execute one by in databases.
Refer to the following link.
http://msdn.microsoft.com/en-us/library/ms176064.aspx
--- Babu
March 22, 2012 at 10:18 am
Babu,
Thanks for the reply.
The application db's are the following size:
1. 12 GB MDF, 23 GB LDF
2. 6 GB MDF, 17 GB LDF
3. 1 GB both
4. < 1 GB both
5 < 1 GB both
Of course, I'll be running this in a maintenance window in the future, or as you suggest to copy off the production server and run.
At this point, I'm trying to do some root cause of what happened when I ran the Maintenance Plan. Would it seem possible for the page file to fill and memory to hit 100% when running a CheckDB maintenance plan?
Thanks for any input.
Dan
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply