BUG: Transfer From Sybase System10 to SQL Server 6.5

Last reviewed: April 8, 1997
Article ID: Q151520

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG#: 15147 (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' listbox 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.

WORKAROUND

Use BCP utility instead.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kb3rdparty kbbug6.50 kbtool SSrvEntMan
Version : 6.5
Platform : WINDOWS

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: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.