BUG: Placing tempdb in RAM Requires Twice the Configuration Size (231646)
The information in this article applies to:
This article was previously published under Q231646
BUG #: 17210 (SQLBUG_65)
SYMPTOMS
Attempting to create a large tempdb database IN RAM may fail because of a lack of memory to support double the configuration value.
CAUSE
When placing the tempdb database IN RAM, the amount configured to use for the tempdb is incorrectly doubled.
For example, if you specify an 800 megabyte (MB) tempdb IN RAM size, the SQL Server incorrectly sees this as 1600 MB.
WARNING: You must never configure tempdb for use in RAM on a clustered SQL Server server.
If you do configure tempdb for use in RAM and you do not remove tempdb from RAM prior to unclustering SQL, you will not be able to recluster the SQL Server server.
WORKAROUND
To work around this problem, use either of these methods:
- Do not place the tempdb database IN RAM and allow a larger data cache to handle the tempdb pages.
-or- - If you are using the standard edition of Microsoft Windows NT, you may want to use the Enterprise Edition instead because it can provide a larger memory footprint.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5.
Modification Type: | Major | Last Reviewed: | 9/25/2003 |
---|
Keywords: | kbBug kbnofix KB231646 |
---|
|