sql server 2000 sp4 build 2184
runs stats with maintenance plan
sp_msforeachtable
stored procedure updating full stats for each table and the results
are identical
A floating point exception occurred in the user process. Current
transaction is canceled.
all pointers are to move to latest service pack
Any pointers on how to avoid this error
Thanks for your time
Massa
Massa Batheli (mngong@gmail.com) writes:
> sql server 2000 sp4 build 2184
>
> runs stats with maintenance plan
> sp_msforeachtable
> stored procedure updating full stats for each table and the results
> are identical
>
> A floating point exception occurred in the user process. Current
> transaction is canceled.
>
> all pointers are to move to latest service pack
> Any pointers on how to avoid this error
It could certainly help if you could give some more detail. Do you get
the error when you run the maintenance plan? Or was running the maintenance
plan an attempt to cure the problem?
If it happens with a query, to try narrow down the query by exluding
columns or rows. Or even tables.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downlo ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books .mspx
Erland Thanks for your response as usual
The maintenance plan was intended to troubleshoot the process .
Mike
On Aug 20, 5:34 pm, Erland Sommarskog
> MassaBatheli (mng...@gmail.com) writes:
> > sql server 2000 sp4 build 2184
>
> > runs stats with maintenance plan
> > sp_msforeachtable
> > stored procedure updating full stats for each table and the results
> > are identical
>
> > A floating point exception occurred in the user process. Current
> > transaction is canceled.
>
> > all pointers are to move to latest service pack
> > Any pointers on how to avoid this error
>
> It could certainly help if you could give some more detail. Do you get
> the error when you run the maintenance plan? Or was running the maintenance
> plan an attempt to cure the problem?
>
> If it happens with a query, to try narrow down the query by exluding
> columns or rows. Or even tables.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/down loads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/boo ks.mspx
Massa Batheli (mngong@gmail.com) writes:
> Erland Thanks for your response as usual
> The maintenance plan was intended to troubleshoot the process .
I don't think floating-point errors are due to poor statistics or
fragmented indexes. You may be able to get rid of the error that
way if you get a different plan, that does not provoke the error.
But in that case, you never know when it comes back and bite you
again.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downlo ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books .mspx
Not been able to eliminate the error for months now .Strongly
considering calling MSFT but would want to be sure it is not something
that is an error of mine.Had some one reinstall sp4 when just in case
it was a fluke during my install but that did not take care of it
either .
Thanks again for your input
Not sure why about the floating point error.Started when there was an
upgrade to sp4 build 2187
Excuse me if this was posted earlier could not find it when I queried
google groups
Was considering calling MSFT but did not want to pay the per call fee
on something some
more knowledgeable person out here could help with ...
Mike
Massa Batheli (mngong@gmail.com) writes:
> Not sure why about the floating point error.Started when there was an
> upgrade to sp4 build 2187
>
> Excuse me if this was posted earlier could not find it when I queried
> google groups
>
> Was considering calling MSFT but did not want to pay the per call fee
> on something some
Notice that if the error is due to a bug in SQL Server, you will be
refunded.
> more knowledgeable person out here could help with ...
Sure. If you provide information to work from. Ideally, that would be
a CREATE TABLE script, INSERT statements with sample data and a query
that reproduces the error. I reckon that this may be difficult to
achieve. But you could at least provide the table and index definitions
and the query where it happens. No one is going to help you if all you
say is that you get a floating point exception.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downlo ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books .mspx