You might also experience this problem while creating a primary key constraint, or when you run the DBCC DBREINDEX command against a permanent table. You will not experience this problem with temporary tables.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This fix introduces a change in functionality for SQL Server trace flag 1118 on SQL Server 7.0 only. When you turn on trace flag 1118, all allocations for tables in the tempdb database will allocate full extents to the table. However, allocations for small tables (less than 8 pages) in other databases will continue to allocate single pages from "mixed" extents exactly as they would if the trace flag were not turned on. The behavior of SQL Server trace flag 1118 on SQL Server 2000 remains unchanged. If SQL Server trace flag 1118 is enabled on SQL Server 2000, mixed extent allocations are disabled in all databases.
SQL Server trace flag 1118 is used to reduce allocation contention in tempdb.
For additional information about troubleshooting problems with allocation contention in tempdb, click the following article number to view the article in the Microsoft Knowledge Base:
328551 Concurrency Enhancements for the Tempdb Database