FIX: CREATE INDEX Statement with Parallel Plan May Stop Responding If Disk Space Is Almost Full (317710)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions) SP1
This article was previously published under Q317710
BUG #: 356645 (SHILOH_BUGS)
SYMPTOMS
The processor (CPU) usage may spike between 50% and 100% and the process may stop responding for a CREATE INDEX statement if all these conditions are true: - SQL Server 2000 Service Pack 1 (SP1) is the current service pack version.
- Execution of this code on the database reports a negative unallocated space:
EXEC sp_spaceused
- There is only a small amount of space available in each file.
- The server has four (4) or more processors and the max degree of parallelism option is set between 4 and 8 or 0 (use all processors).
- A parallel plan is chosen for the CREATE INDEX statement.
CAUSE
The sysindexes system table contains incorrect values for the number of reserved pages for each table in the database. The incorrect value causes the sp_spaceused stored procedure to report a negative number for the unallocated space.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
To work around this problem, run this code to correct the available space information in the sysindexes table:
EXEC sp_spaceused @updateusage = 'TRUE'
After no negative unallocated disk space is reported, the CREATE INDEX statement terminates with the following error message if there is not enough disk space:
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'index_name' in database 'dbname' because the 'PRIMARY' filegroup is full.
The statement has been terminated.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
Modification Type: | Major | Last Reviewed: | 4/10/2002 |
---|
Keywords: | kbbug kbSQLServ2000SP2Fix KB317710 |
---|
|