Floating point exception on SQL 2000 SP4 2187

Question

Floating point exception on SQL 2000 SP4 2187

mngong

SSCertifiable

Points: 6167
More actions
March 12, 2007 at 8:25 am

#172452

Ran full stats on sp4 as shown below
EXEC dbo.sp_MSforeachtable @command1 = "UPDATE STATISTICS ? WITH FULLSCAN, ALL"
and receive this error in return
Executed as user: CROWN\mssqlaccount. A floating point exception occurred in the user process. Current transaction is canceled. [SQLSTATE 42000] (Error 3628).
Google and MSFT all say patch to SP4 but the system is patched already
Your input is appreciated

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

EdVassie SSC Guru Points: 60472 More actions · Answer 1

This probably should be reported as a bug to Microsoft.

I think sp_MSforeachtable is not officially supported by Microsoft. Therefore you will need to isolate where you get the fp execption, and show it happening using fully supported code.

You may be able to re-create the problem in a maintenance plan. If so, this would count as supported code.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

noeld SSC Guru Points: 96590 More actions · Answer 2

In addition @command1 expects a varchar the correct way is :

EXEC dbo.sp_MSforeachtable @command1 = 'UPDATE STATISTICS [?] WITH FULLSCAN, ALL'

by the way I have SP4 and have no issues with that command.

Do you have Indexed Views or Computed Columns ?

* Noel

mngong SSCertifiable Points: 6167 More actions · Answer 3

Not sure it does .But a maintenance plan is in place to do the same job

You will be informed if that works

Thanks for your time

Mike

noeld SSC Guru Points: 96590 More actions · Answer 4

If you have Indexed views or Computed colums you need to have the correct "SET" environment:

set ansi_nulls on

set quoted_identifier on

set ansi_warnings on

set ansi_padding on

set arithabort on

set concat_null_yields_null on

set numeric_roundabort off

Cheers,

* Noel

mngong SSCertifiable Points: 6167 More actions · Answer 5

Made modifications suggested by noeld and the error reccurs

The maintenance plan failed with the same error

Will try to run for individual tables

Mike

mngong SSCertifiable Points: 6167 More actions · Answer 6

Tried the run for individual tables and it succeeded for most of them.The error appeared after one of them but the dbcc checktable for the table for the particular table

did not return any errors

TIA

Mike