May 23, 2013 at 10:21 am
DBCC checkDB is filling up the tempDB. Weird fact is we have a database around 1 TB and its taking 20 GB of tempdb but for a 160 GB database its filling up 40GB+ tempdb and the checks are failing.
As we all know there is a bug in 2008R2 and I cant estimate how much tempdb gonna grow. Monitored memory counters using perfmon and the server doesnt has any memory pressure.
Appreciate any replies.
May 23, 2013 at 2:20 pm
ErrLog (5/23/2013)
DBCC checkDB is filling up the tempDB. Weird fact is we have a database around 1 TB and its taking 20 GB of tempdb but for a 160 GB database its filling up 40GB+ tempdb and the checks are failing.As we all know there is a bug in 2008R2 and I cant estimate how much tempdb gonna grow. Monitored memory counters using perfmon and the server doesnt has any memory pressure.
Appreciate any replies.
Are you doing a DBCC checkdb of a 1TB live database? If yes, you should backup and restore and do that offline or on a different server. That database is too big for that, you will affect other users.
I personally do not run DBCC command unless is a very small database and I believe it's damaged or it's needed. I prefer to backup and restore on a different place and do all my checks there.
Take a look on this useful article from Paul Randal: http://www.sqlskills.com/blogs/paul/checkdb-from-every-angle-consistency-checking-options-for-a-vldb/%5B/url%5D
May 23, 2013 at 3:03 pm
We do it during weekends and it usually takes 20 hrs. No additional storage for restore.
But the point is for 1TB database it is taking 20GB tempdb and DBCC is successful.
For the other database which is around 160GB, its filling up whole tempdb (40GB) and it fails.
May 23, 2013 at 8:32 pm
ErrLog (5/23/2013)
We do it during weekends and it usually takes 20 hrs. No additional storage for restore.But the point is for 1TB database it is taking 20GB tempdb and DBCC is successful.
For the other database which is around 160GB, its filling up whole tempdb (40GB) and it fails.
You may have different Indexes. And activity and concurrency it's not the same.
Do a physical only check. That database is too big for a regular DBCC. Or do it bi-weekly or monthly.
I think more important than that is check your backups.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply