I have a SQL job that runs as part of a nightly load of data tables. Part
of the job is a DTS job (loading a table from a text file), and other parts
of it are either sql code, or calling of a stored procedure.

We have 2 production servers, both (I thought) set up identically. SQL
2000, most recent service packs.

However, 2 times in the last several weeks, (3 times overall) we've gotten
this error in the same spot:

"A floating point exception occurred in the user process. Current
transaction is canceled. [SQLSTATE 42000] (Error 3628). The step failed."

We went back & checked the source table for it, and saw no problems.

We took the same job (a collection of about 10 stored procedure calls) that
looked like this:

sp_build_table_1
go
sp_build_table_2
go
sp_build_table_3
go
and so on....

and pulled it into query analyzer.

When run in Query Analyzer from a desktop (not the server), the jobs run
fine - no floating point exceptions or anything.

Any ideas as to what the problem might be? Not sure if it is a dts problem,
a programming problem or just a server setup issue.

Thanks,

SC

SC,

There are several reasons that this might manifest itself that have nothing
to do with the data and everything to do with the complexity of a query.
You might check out these KB articles and see if they help.

http://support.microsoft.com/default...b;en-us;818899
http://support.microsoft.com/default...b;en-us;829444
http://support.microsoft.com/default...b;en-us;812995
http://support.microsoft.com/default...b;en-us;816503

Russell Fields
"Goober" <me (AT) privacy (DOT) net> wrote