Microsoft KB Archive/167753

= BUG: Transfer from Sybase System10 to SQL Server 6.5 =

Article ID: 167753

Article Last Modified on 10/3/2003

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q167753



BUG #: 15147 (SQLBUG_65)



SYMPTOMS
From the transfer management interface within SQL Server 6.5 Enterprise Manager, if you specify a Sybase System10 server as the source, all objects in the source database come up in the Add/Remove Objects list box as User Defined Datatype. This makes it impossible to transfer tables, stored procedures, and so forth between Sybase System10 and SQL Server 6.5 using the transfer management interface.



CAUSE
In Sybase System10 on the UNIX platform (NLM, R6000, SUN, and so on), when bitwise operation is performed with hex number, it always returns 0; for example, (15 & 0xf) returns 0 instead of 15. SQL Server 6.5 Enterprise Manager transfer interface uses (sysobjects.sysstat & 0xf) to determine object type, hence the problem.



WORKAROUND
To work around this problem, use the bulk copy program (BCP) utility instead.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5.



MORE INFORMATION
SQL Server 6.0 transfer manager works fine because it uses (sysobjects.sysstat & 15) to determine the object type. The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Additional query words: GUI copy move graphical dialog system 10

Keywords: kbbug kbinterop kb3rdparty kbpending KB167753

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.