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. CAUSEThis method uses the ODBC BCP API, which does not provide for code page conversion in this circumstance. RESOLUTIONA 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. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later: NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.STATUSMicrosoft 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. Additional query words: cp cs dbcs OemToAnsi AutoAnsiToOem nls charset character set Transfer Manager
Keywords : SSrvDMO SSrvProg SSrvTrans kbbug7.00 kbSQLServ700bug |
Last Reviewed: January 3, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |