SQL Server: small TEMPDB causes DBCC Errors

If you get the following DBCC CHECKDB errors, then the problem could simply be a small TEMPDB. I've BOLDEN the really important clue at the end of the error stack.

This was really annoying!!!!!

 Msg 8964, Level 16, State 1, Line 1

Table error: Object ID 630097831, index ID 1, partition ID 72057653728051200, alloc unit ID 72057594343129088 (type LOB data). The off-row data node at page (1:35728379), slot 0, text ID 1055064064 is not referenced.

Msg 2534, Level 16, State 2, Line 1

Table error: page (1:35797497), whose header indicates that it is allocated to object ID 630097831, index ID 1, partition ID 72057653728051200, alloc unit ID 72057594343129088 (type LOB data), is allocated by another object.

Msg 2533, Level 16, State 1, Line 1

Table error: page (1:34608553) allocated to object ID 630097831, index ID 1, partition ID 72057653728051200, alloc unit ID 72057594343129088 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

Msg 8965, Level 16, State 1, Line 1

Table error: Object ID 630097831, index ID 1, partition ID 72057653728051200, alloc unit ID 72057594343129088 (type LOB data). The off-row data node at page (1:33939922), slot 0, text ID 944701440 is referenced by page (1:36219352), slot 4, but was not seen in the scan.

Msg 2533, Level 16, State 1, Line 1

Table error: page (1:34616630) allocated to object ID 630097831, index ID 1, partition ID 72057653728051200, alloc unit ID 72057594343129088 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

CHECKDB found 0 allocation errors and 3366 consistency errors in table 'XX' (object ID 630097831).

CHECKDB found 0 allocation errors and 3366 consistency errors in database 'DB'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DB).

Msg 9002, Level 17, State 4, Line 1

The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'.