This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 82%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETW%3C/text%3E%3C/svg%3E)
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.
If CU11 doesn't resolve the issue, try tweaking DATABASE SCOPED CONFIGURATION options as a possible work-around. Try TSQL_SCALAR_UDF_INLINING = OFF for starters and, if that doesn't work, BATCH_MODE_ON_ROWSTORE = OFF.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 30%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
... and since FREETEXTTABLE is about full-test indexes, perhaps rebuild the full-text index in question?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 78%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECZ%3C/text%3E%3C/svg%3E)
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
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.