Article ID: 294999 - View products that this article applies to.
This article was previously published under Q294999
BUG #:352303 (SHILOH_BUGS)
On Microsoft Windows 2000 Datacenter computers with 24 or more CPUs, an attempt to start SQL Server in minimal configuration
may fail with the following error in the SQL Errorlog:
2001-02-15 12:55:18.04 spid5 Could not create worker thread.
2001-02-15 12:55:18.09 spid5 Could not find database ID 2. Database may not be activated yet or may be in transition.
During SQL Server startup, there are several operations that consume threads, such as creating files, zeroing files, deleting files, and so on. Because the number of threads is determined in part by the number of CPUs, more threads are needed as the number of CPUs increases. When starting SQL Server normally, this is not a problem because SQL Server always has 255 threads available. When starting SQL Server with the minimum configuration setting, however, there are only 32 threads to be divided among the total number of processors and associated operations.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
Article ID: 294999 - Last Review: February 22, 2007 - Revision: 3.3
Contact us for more help