PRB: Transfer from Sybase System10 to SQL Server 6.5

 Last reviewed: May 1, 1997
Article ID: Q167753
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

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 system 10 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.

MORE INFORMATION

SQL Server 6.0 transfer manager works fine because it uses (sysobjects.sysstat & 15) to determine the object type.

Additional query words: GUI copy move graphical dialog
Keywords : SSrvDMO SSrvEntMan kb3rdparty kbinterop
Version : 6.5
Platform : WINDOWS
Issue type : kbprb
Solution Type : kbworkaround

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.