Microsoft KB Archive/940375

= FIX: Error message when you use the Copy Database Wizard to move a database from SQL Server 2000 to SQL Server 2005 =

Article ID: 940375

Article Last Modified on 8/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Service Pack 2

-



Bug #: 50001412 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SYMPTOMS
In SQL Server 2005, you use the Copy Database Wizard to move a database from Microsoft SQL Server 2000 to SQL Server 2005. However, the operation fails, and you receive the following error message:

Message: ERROR : errorCode=-1073548784 description=Executing the query &quot;IF EXISTS (SELECT name FROM sys.databases WHERE name = N'copywizard')

DROP DATABASE [copywizard]

&quot; failed with the following error: &quot;Cannot drop database &quot;copywizard&quot; because it is currently in use.&quot;. Possible failure reasons: Problems with the query, &quot;ResultSet&quot; property not set correctly, parameters not set correctly, or connection not established correctly.

If you run SQL Server Profiler when this problem occurs, you notice that the Data Transformation Services (DTS) package has generated a rollback transaction event before the error occurs.



RESOLUTION
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



WORKAROUND
To work around this problem, split the database objects into subsets. Then, create smaller Microsoft SQL Server 2005 Integration Services (SSIS) packages to move each subset separately.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

