This article was previously published under Q236868
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55636 (SQLBUG_70)
The SQL Distributed Management Objects (DMO) Transfer method does not perform code page conversion when transferring non-Unicode character data from one SQL Server 7.0 to another with a different code page.
In addition, the Data Transformation Services (DTS) Object Transfer feature (the transfer option titled "Transfer objects and data between SQL Server 7.0 databases" in the DTS Import/Export Wizard) depends on this DMO method, so it will not perform code page translation, either.
This method uses the ODBC BCP API, which does not provide for code page conversion in this circumstance.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
The other transfer options available in the DTS Import/Export Wizard ("Copy tables(s) from the source database" and "Use a query to specify the data to transfer") do not depend on SQL-DMO, and will perform code page conversion if the Auto Translate property is set to 1 for each connection by clicking on the Advanced button. This property has no effect when DTS Object Transfer ("Transfer objects and data between SQL Server 7.0 databases") is used.
The fix for the SQL-DMO Transfer method allows this method to perform code page translation in all cases. In other words, when using the DTS Object Transfer option in the DTS Import/Export Wizard, the "Auto Translate" option still does not have any effect.
cp cs dbcs OemToAnsi AutoAnsiToOem nls charset character set Transfer Manager