BUG: (DOC) Description of Sysaltfiles Table Incorrect (233232)


The information in this article applies to:

  • Microsoft SQL Server 7.0
This article was previously published under Q233232
BUG #: 55622 (SQLBUG_70)

SYMPTOMS

According to the SQL Server 7.0 Books online (BOL), the sysaltfiles system table, "Contains one row for each file in a database". This description is not correct, as the sysaltfiles table contains rows for databases only under special circumstances:
  • To store the file entries for the tempdb database. These entries, except for situations in which data or log file drops have not been successful, correspond directly to the entries in the tempdb..sysfiles1 table. The sysfiles1 table in tempdb is populated from the master..sysaltfiles table for dbid 2 upon server startup.

  • In disaster recovery situations in which recovery is not able to complete because we have run out of room on disk. If we take steps to move or add a new file to the database, the new entries for the file are stored in the sysaltfiles table. These entries are moved from sysaltfiles to the database's sysfiles1 table upon successful server startup.

  • For READONLY databases whose files are relocated. When speaking of readonly databases, we are considering those that are not only configured to be read-only, but additionally, are located on updateable media, such as CDs.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0.

MORE INFORMATION

NOTE: The sysaltfiles table is used and maintained exclusively by the system. You should not attempt to modify the contents of the sysalfiles table either manually or programmatically. The purpose of this article is strictly informational.

REFERENCES

For more information on recovering from Insufficient Disk Space, please refer to the following:

SQL Server Books Online; search on "Insufficient Disk Space"
Modification Type:MajorLast Reviewed:10/16/2002
Keywords:kbBug kbdocerr KB233232
©2002 Microsoft Corporation. All rights reserved.