FIX: Error message when you run the DBCC CHECKTABLE statement or the DBCC CHECKDB statement in Microsoft SQL Server 2005: "Column '<ColumnName>' value is out of range for data type 'float'"

Article translations Article translations
Article ID: 942904 - View products that this article applies to.
Bug: #50001847 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

In Microsoft SQL Server 2005, when you run the DBCC CHECKTABLE statement or the DBCC CHECKDB statement to perform a physical consistency check on a table, you receive an error message that resembles the following error message:
DBCC results for '<TableName>'.
Msg 2570, Level 16, State 3, Line 1 Page (1:73), slot 2 in object ID 2073058421, index ID 1, partition ID 72057594038321152, alloc unit ID 72057594043301888 (type "In-row data"). Column "<ColumnName>" value is out of range for data type "float". Update column to a legal value.
Note In this error message, TableName represents the actual name of the table, and ColumnName represents the actual name of the column.

CAUSE

This problem occurs because an INSERT statement or an UPDATE statement passes values that are out of range into a column that is a FLOAT data type column. This condition may occur if the INSERT statement or the UPDATE statement does not send the values that are inserted or that are updated as literals. For example, this issue may occur if you use a variable to pass an invalid value into an INSERT statement or into an UPDATE statement.

RESOLUTION

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you apply this hotfix, SQL Server does not prevent you from entering invalid values in columns that are FLOAT data type columns. After you apply this hotfix, the invalid values are not indicated as errors in the DBCC CHECKTABLE statement or in the DBCC CHECKDB statement.

Steps to reproduce the problem

  1. Open SQL Server Management Studio, and then connect to an instance of SQL Server 2005.
  2. Create a new query, and then run the following statements:
    create table tb1 (c float)
    go
    
    declare @f float
    set @f=1E-307*0.01
    insert tb1 values (@f)
    go
    select * from tb1
    go
    Notice that the following invalid value has been inserted into the table:
    1E-309
  3. Run the following statements:
    DBCC CHECKTABLE ('tb1')
    go
    You receive the error message that the "Symptoms" section describes.
  4. Run the following statements:
    insert tb1 values (1E-309)
    go
    You receive one of the following messages, depending on the SQL Server build:

    Message 1
    Warning: the floating point value '1E-309' is too small. It will be interpreted as 0.
    Message 2
    The floating point value '1E-309' is out of the range of computer representation (8 bytes).
    In this case, the invalid value is not inserted into the table because you send the value as a literal.
  5. Run the following statements to examine the value that is inserted into the table in step 4:
    select * from tb1
    go
    Notice that 0 is inserted instead of the invalid value.

REFERENCES

For more information about how to troubleshoot DBCC error 2750 (data purity), click the following article number to view the article in the Microsoft Knowledge Base:
923247 Troubleshooting DBCC error 2570 in SQL Server 2005
For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=71711
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 942904 - Last Review: November 14, 2007 - Revision: 2.4
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
Keywords: 
kbsql2005engine kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced KB942904

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