BUG: File growth value for the tempdb database is not persistent when changed from fixed increments to percentage (816939)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
SQL Server 8.0 450066 SYMPTOMSWhen you change the file growth value for the tempdb database file from fixed increments to percentage and you restart
SQL Server, the file growth value still appears in fixed increments (for
example 80 KB).CAUSEThis behavior may occur if the status column in the sysaltfiles table of the master database is not correctly updated to reflect the file growth
percent for the tempdb database file.WORKAROUNDTo work around the problem, update the status column in the sysaltfiles table of the master database. To do so, follow these steps: Warning: The following steps contain information about modifying system
tables. SQL Server may not be stable if the system tables are updated
incorrectly. Microsoft cannot guarantee the resolution of problems that occur
because system tables were updated incorrectly. - Make sure that the growth column in the tempdb..sysfiles and the master..sysaltfiles tables has the percent value you specified (for example x for x
percent).
- Run the following code in Query Analyzer:
use master go sp_configure 'allow updates', 1 go reconfigure with override go update sysaltfiles set status = 1048578 where fileid = <fileid1> and name = '<data filename>' go update sysaltfiles set status = 1048642 where fileid = <fileid2> and name = '<log filename>' go checkpoint go sp_configure 'allow updates', 0 go reconfigure with override go where the <fileid1> and <fileid2> are the file ids that correspond to the data and the log
files according to the sysaltfiles table.
The <data file name> and the <log filename> are the names (the name column value of the sysaltfiles table) of the data and the log files respectively. - Restart SQL Server.
- Verify the file growth value for the tempdb database files. To verify the growth value, run the following
code in Query Analyzer:
exec sp_helpdb tempdb
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.REFERENCESFor more information about the ALTER DATABASE command, visit
the following MSDN Web site:
Modification Type: | Major | Last Reviewed: | 11/17/2005 |
---|
Keywords: | kbSysAdmin kbBug kbcode kbprb KB816939 kbAudDeveloper |
---|
|