the 'DEFAULT' filegroup is full

[pardhi a via SQLMonster.com]

Server: Msg 1105, Level 17, State 2, Line 2
Could not allocate space for object '(SYSTEM table id: -276436763)' in
database 'TEMPDB' because the 'DEFAULT' filegroup is full.
this error occured during dbcc checkdb the total size of the file we are
doing on is [81GB].

what is the next step we need to take
we increased about 3699.mb in temp db
overall we have 8 databases in our server
anyone help would me much appreciated.

Thanks,
pardhi
--
Message posted via http://www.sqlmonster.com

[Simon Hayes]

You could run DBCC CHECKDB WITH ESTIMATEONLY to see what the estimated
tempdb size is, then increase it to at least that size.

Simon

[pardhi a via SQLMonster.com]

I did that it is showing almost the original file tha tis [81GB].
is there any other way

once agian thanks simon

Simon Hayes wrote:

You could run DBCC CHECKDB WITH ESTIMATEONLY to see what the estimated
tempdb size is, then increase it to at least that size.

Simon

--
Message posted via http://www.sqlmonster.com

[Simon Hayes]

You could use NOINDEX or PHYSICAL_ONLY to do a more 'lightweight' check
- that might reduce the required space, and unless you suspect you have
a problem that might be good enough for you.

In the worst case, you could run DBCC CHECKALLOC and then write a loop
to run DBCC CHECKTABLE for each table - that's equivalent (as far as I
know, but I have to admit I'm not entirely sure) to running DBCC
CHECKDB.

Simon

[pardhi a via SQLMonster.com]

Yes there is a prob in the DB.i copied the backup file in testing server and
run checkdb dbcc checkdb fix that error but this is a long process.

looks like need to give some more space in tempdb.[81GB] but my collegue (dba)
is not accepting that way is there any other way.

Thanks simon

Simon Hayes wrote:

You could use NOINDEX or PHYSICAL_ONLY to do a more 'lightweight' check
- that might reduce the required space, and unless you suspect you have
a problem that might be good enough for you.

In the worst case, you could run DBCC CHECKALLOC and then write a loop
to run DBCC CHECKTABLE for each table - that's equivalent (as far as I
know, but I have to admit I'm not entirely sure) to running DBCC
CHECKDB.

Simon

--
Message posted via http://www.sqlmonster.com