Share via

SQL Server Floating Point Exception

Tony Wu 1 Reputation point
2021-08-02T02:05:58.503+00:00

When run a simple query against a full text search table, I got a floating point error. See below sql statement and error message.

Query:
SELECT TOP 10 * FROM FREETEXTTABLE (dbo.FreeTextTable, (F1, F2, F3, Fr), 'Keyword here') AS ft

Error Message
Msg 3628, Level 16, State 1, Line 1
The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator.

My SQL Server version is:
SELECT @@VERSION
GO

Microsoft SQL Server 2019 (RTM-CU10) (KB5001090) - 15.0.4123.1 (X64)
Mar 22 2021 18:10:24
Copyright (C) 2019 Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2019 Datacenter 10.0 <X64> (Build 17763: ) (Hypervis

Can you help check? Thank you in advance.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,367 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Cris Zhan-MSFT 6,616 Reputation points
    2021-08-02T06:27:17.503+00:00

    Hi,

    Please try to apply the latest Cumulative Update package (CU11) for your SQL Server 2019 instance first.
    https://support.microsoft.com/en-us/topic/kb5003249-cumulative-update-11-for-sql-server-2019-657b2977-a0f1-4e1f-8b93-8c2ca8b6bef5#bkmk_14015202

    0 comments
  2. Erland Sommarskog 107.2K Reputation points
    2021-08-02T09:10:52.207+00:00

    Do you have a repro? That is, a simple script that builds a database, populates a table, creates a full-text index and then runs a query that produces this error?

    I would not really expect that it is simple to produce such a repro, as it is likely to be dependent on your data and maybe a few more circumstances.

    As Cris says, first apply CU11 just to see if this may fix the issue.

    But if that does not work out, I would recommend that you open a support case. Assuming that it is a bug in the product, the support case should be of no cost for you at the end.

    There is a small risk that it is due to corruption of some sort, so you could run DBCC CHECKDB on the database before you open a support case. You could also work on a copy of the database where you drop and recreate the full-text index.

    0 comments