BUG: Transfer from Sybase System10 to SQL Server 6.5

• 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 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 version 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 discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words: GUI copy move graphical dialog system 10

Keywords          : kb3rdparty kbinterop SSrvDMO SSrvEntMan 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: July 8, 1999