FIX: Database Files Are Created in the Wrong Folder During the Creation of a New Database on a Named Instance (308806)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q308806
BUG#: 353591 (SHILOH_BUGS)

SYMPTOMS

In Data Transformation Services (DTS) on a named instance of SQL Server 2000, when you click <new> to create a new database in the Connection Properties dialog box, the database files are not created in the default data folder. This problem only occurs with a named instance of SQL Server and does not occur with a default instance of SQL Server.

The database files are created in the following folder:

Program Files\Microsoft SQL Server\MSSQL$instance name

The correct location of the new database files is the Data folder:

Program Files\Microsoft SQL Server\MSSQL$instance name\Data

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

WORKAROUND

You cannot change the location files for the new database in the Connection Properties dialog box. However, after you create the database, you can "detach" it, move the files to the correct location, and then "attach" it back to SQL Server.
  1. Detach the database: In Enterprise Manager, press and hold down the ALT key while you click the database name, click All Tasks, and then click Detach Database.
  2. In Windows Explorer, move the .mdf data file and the .ldf transaction log file to the correct location.
  3. Attach the database: In Enterprise Manager, press and hold down the ALT key while you click the database folder, click All Tasks, and then click Attach Database. Click the ellipsis button (...) to browse to the new location, and then select the .mdf file for the database. Click OK to close the Attach Database dialog box.

STATUS

Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
Modification Type:MajorLast Reviewed:10/16/2003
Keywords:kbbug kbfix KB308806
©2003 Microsoft Corporation. All rights reserved.