BUG: DMO Transfer Methods Does Not Do Code Page Conversion

ID: Q236868

The information in this article applies to:
BUG #: 55636 (SQLBUG_70)

SYMPTOMS

The SQL Distributed Management Objects (DMO) Transfer method does not do 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.


CAUSE

This method uses the ODBC BCP API, which does not provide for code page conversion in this circumstance.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later: 

   Date       Time        Version   Size       File name   Platform
   ----------------------------------------------------------------

   06/17/1999 3:06:14 PM  7.00.701  2,617,344  SQLDMO.DLL  Intel
   06/17/1999 3:06:20 PM  7.00.701  94,208     SQLSVC.DLL  Intel
   06/17/1999 3:04:56 PM  7.00.701  4,713,472  SQLDMO.DLL  Alpha
   06/17/1999 3:05:04 PM  7.00.701  112,640    SQLSVC.DLL  Alpha
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

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


MORE INFORMATION

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.

Additional query words: cp cs dbcs OemToAnsi AutoAnsiToOem nls charset character set Transfer Manager 


Keywords          : SSrvDMO SSrvProg SSrvTrans kbbug7.00 kbSQLServ700bug 
Version           : WINDOWS:1.0; winnt:7.0
Platform          : WINDOWS winnt 
Issue type        : kbbug

Last Reviewed: August 12, 1999