FIX: Using ALTER TABLE to Change Column Type Can Result in Unexpected NULL Values on INSERT

Article translations Article translations
Article ID: 279296 - View products that this article applies to.
This article was previously published under Q279296
BUG #: 236443 (shiloh_bugs)
Expand all | Collapse all

On This Page

SYMPTOMS

If the column type of a table is changed by using an ALTER TABLE statement, a subsequent INSERT statement may incorrectly insert a NULL value instead of the value supplied in the INSERT statement.

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 1.

The English version of this fix should have the following file attributes or later:
   Version       File name     Platform
   ------------------------------------

   8.00.217      S80217i.exe   Intel
				
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

WORKAROUND

Create a new table with desired column types and copy the original table into the new table.

STATUS

Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

Properties

Article ID: 279296 - Last Review: November 6, 2003 - Revision: 3.1
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbbug kbfix kbqfe kbsqlserv2000sp1fix KB279296

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com