5  

This is happening cause certain steps in an execution plan can trigger writes to tempdb in particular certain sorts and joins involving lots of data.

發生這種情況會導致執行計划中的某些步驟觸發對tempdb的寫入，特別是涉及大量數據的某些排序和連接。

Since you are sorting a table with a boat load of columns, SQL decides it would be crazy to perform the sort alone in temp db without the associated data. If it did that it would need to do a gazzilion inefficient bookmark lookups on the underlying table.

由於您正在使用列加載列對表進行排序，因此SQL決定在沒有關聯數據的情況下在temp db中單獨執行排序會很瘋狂。如果它這樣做，它將需要在基礎表上進行一個低效的書簽查找。

Follow these rules:

遵循以下規則：

1. Try to select only the data you need
2. 嘗試僅選擇所需的數據
3. Size tempdb appropriately, if you need to do crazy queries that sort a gazzilion rows, you better have an appropriately sized tempdb
4. 適當地調整tempdb的大小，如果你需要做一個對gazzilion行進行排序的瘋狂查詢，你最好有一個適當大小的tempdb

4  

Usually, tempdb fills up when you are low on disk space, or when you have set an unreasonably low maximum size for database growth. Many people think that tempdb is only used for #temp tables. When in fact, you can easily fill up tempdb without ever creating a single temp table. Some other scenarios that can cause tempdb to fill up:

通常，當磁盤空間不足時，或者為數據庫增長設置了不合理的低最大大小時，tempdb會填滿。許多人認為tempdb僅用於#temp表。實際上，您可以輕松填充tempdb而無需創建單個臨時表。其他一些可能導致tempdb填滿的場景：

• any sorting that requires more memory than has been allocated to SQL Server will be forced to do its work in tempdb;
• 任何需要比分配給SQL Server更多內存的排序將被強制在tempdb中完成它的工作;
• if the sorting requires more space than you have allocated to tempdb, one of the above errors will occur;
• 如果排序需要的空間比分配給tempdb的空間多，則會出現上述錯誤之一;
• DBCC CheckDB('any database') will perform its work in tempdb -- on larger databases, this can consume quite a bit of space;
• DBCC CheckDB（'任何數據庫'）將在tempdb中執行其工作 - 在較大的數據庫上，這可能會消耗相當多的空間;
• DBCC DBREINDEX or similar DBCC commands with 'Sort in tempdb' option set will also potentially fill up tempdb;
• DBCC DBREINDEX或具有'Sort in tempdb'選項集的類似DBCC命令也可能填滿tempdb;
• large resultsets involving unions, order by / group by, cartesian joins, outer joins, cursors, temp tables, table variables, and hashing can often require help from tempdb;
• 涉及聯合的大型結果集，按組/順序排列，笛卡爾連接，外連接，游標，臨時表，表變量和散列通常需要tempdb的幫助;
• any transactions left uncommitted and not rolled back can leave objects orphaned in tempdb;
• 任何未提交且未回滾的事務都可以在tempdb中保留孤立的對象;

• use of an ODBC DSN with the option 'create temporary stored procedures' set can leave objects there for the life of the connection.

  使用帶有“創建臨時存儲過程”選項的ODBC DSN可以在連接的生命周期中保留對象。

  USE tempdb GO

  使用tempdb GO

      SELECT name 
          FROM tempdb..sysobjects 
  
      SELECT OBJECT_NAME(id), rowcnt 
          FROM tempdb..sysindexes 
          WHERE OBJECT_NAME(id) LIKE '#%' 
          ORDER BY rowcnt DESC
  

The higher rowcount, values will likely indicate the biggest temporary tables that are consuming space.

行數越高，值可能表示占用空間的最大臨時表。

Short-term fix

短期修復

DBCC OPENTRAN -- or DBCC OPENTRAN('tempdb')
DBCC INPUTBUFFER(<number>)
KILL <number>

Long-term prevention

長期預防

-- SQL Server 7.0, should show 'trunc. log on chkpt.' 
-- or 'recovery=SIMPLE' as part of status column: 

EXEC sp_helpdb 'tempdb' 

-- SQL Server 2000, should yield 'SIMPLE': 

SELECT DATABASEPROPERTYEX('tempdb', 'recovery')
ALTER DATABASE tempdb SET RECOVERY SIMPLE

Reference : http://sqlserver2000.databases.aspfaq.com/why-is-tempdb-full-and-how-can-i-prevent-this-from-happening.html
Other references : http://social.msdn.microsoft.com/Forums/is/transactsql/thread/af493428-2062-4445-88e4-07ac65fedb76

參考：http：//sqlserver2000.databases.aspfaq.com/why-is-tempdb-full-and-how-can-i-prevent-this-from-happening.html其他參考文獻：http：//social.msdn。 microsoft.com/Forums/is/transactsql/thread/af493428-2062-4445-88e4-07ac65fedb76