BUG: Incorrect Column Mapping: Destination Shows TIMESTAMP From Nullable BINARY Source (275255)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
  • Microsoft SQL Server 7.0
This article was previously published under Q275255
BUG #: 58450 (SQLBUG_70)
BUG #: 236440 (SHILOH)

SYMPTOMS

When you create a Data Transformation Services (DTS) package (either through the DTS Design interface or through the Import Data Wizard), which transfers data from a table with a nullable BINARY source column to a nonnullable BINARY source column, the DTS interface incorrectly shows the column mapping on the destination table to be TIMESTAMP.

WORKAROUND

The base table schemas are not affected by this bug. That is, the package runs correctly, and does not change any base data types in either the source or destination tables. Therefore, to work around this behavior, ignore the column mapping and proceed with the package creation and execution.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create two tables, one with a BINARY field that is nullable named DTS_Nullable, and one with a BINARY() field that is not nullable named DTS_NonNullable.
  2. Populate these tables with data to test the package execution.
  3. In the DTS Designer, create a package that transfers data from the DTS_Nullable table to the DTS_NonNullable table.
  4. When you click the Destination tab in the Transform data Task Properties dialog box, the destination column mapping for the BINARY field displays as a column of data type TIMESTAMP.
  5. Run the package and examine the data in your destination table.
  6. No data types have changed, and all the data was copied intact.
Modification Type:MajorLast Reviewed:10/31/2003
Keywords:kbBug kbpending KB275255
©2003 Microsoft Corporation. All rights reserved.