When you use SQL Server Enterprise Manager to attach multiple database files, which are saved on different hard disk driver folders, the following problems may occur:
- If you create a database for some of the log or data files that are stored in a different directory than the primary database file, after you detach and try to reattach the database the Current File(s) Location check box is selected, which indicates there are invalid filenames that correspond to the files that are not located in the same folder as the primary database file. No ellipsis button is available to browse the file location for the secondary data file and the log file location. If the file location is manually changed to the correct location the attach process completes successfully.
- While reattaching a previously detached database that has only one log file after the log file has been deleted (the engine allows the database to attach and automatically creates a new log file if you do not explicitly specify a log file), the Current File(s) Location check box under the Attach Database dialog box is selected, which indicates invalid filenames correspond to the log file that is not located in the same folder as the primary database file. After you click OK , the single file attachment completes successfully.
- When you attach only a single data file without a log file, changing the database name disables the OK button and the attach process cannot complete.
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:
INF: How to Obtain the Latest SQL Server 2000 Service Pack
You can run the sp_attach_db
stored procedure to attach the database for which some of the log or data files were stored in a different directory than the primary database file.
You can run the sp_attach_single_file_db
stored procedure to attach a single data file.
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: 293329 - Last Review: January 16, 2015 - Revision: 4.0
- Microsoft SQL Server 2000 Standard Edition
|kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB293329|