checkdb filling up tempdb

Hello all,
I have a 10 gig SQL 2000 sp3 database that is having the following problem.
The tempdb which is on the c drive is expanding past two gigs when I run my
checkdb maintenance job. This is filling the c drive and bringing down my
app. I am going to move the tempdb to another drive that has more room but
my question is why would an integrity check fill up the tempdb? I assume
this is the problem since the time stamps for the job and problem are
identical.
TIA
jjThis is By Design. Any of the DBCC checks require space in tempdb for
processing check information - this is documented in Books Online. The
amount of space is proportional to the size of the database being checked,
and the amount of active transaction log for that database. You can use the
WITH ESTIMATEONLY option to find out the minimum amount of space required in
tempdb, not counting that dependant on the transaction log size.
From the numbers you've given, it sounds like you either have a large
active log or one very large table in the database.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:eFjJS2V1DHA.2700@.TK2MSFTNGP11.phx.gbl...
> Hello all,
> I have a 10 gig SQL 2000 sp3 database that is having the following
problem.
> The tempdb which is on the c drive is expanding past two gigs when I run
my
> checkdb maintenance job. This is filling the c drive and bringing down my
> app. I am going to move the tempdb to another drive that has more room but
> my question is why would an integrity check fill up the tempdb? I assume
> this is the problem since the time stamps for the job and problem are
> identical.
> TIA
> jj
>