Microsoft KB Archive/296849

= FIX: BULK INSERT Replaces Current Datetime Column Value with Previous Column Value if Data File Contains All Spaces =

Article ID: 296849

Article Last Modified on 10/9/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q296849



BUG #: 353579 (SQLBUG_2000)

BUG #: 354423 (SQLBUG_2000)



SYMPTOMS
When the BULK INSERT T-SQL command is used to import a datetime value from a character or Unicode file in which neither the date nor time value is provided, and instead space characters exist in the data file for the column, the datetime value from the previous datetime row imported is used. The datetime value, however, should be inserted as NULL because the datetime value did not exist.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

Hotfix
NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.

The English version of this fix should have the following file attributes or later:   File name    Platform -  s80285i.exe  x86 - SQL Server 2000 original release fix s80404i.exe x86 - SQL Server Service Pack 1 fix NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.



WORKAROUND
Use the Bcp.exe command line utility instead of the BULK INSERT command.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix KB296849

-

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

© Microsoft Corporation. All rights reserved.