Floating Point Error - Possibly corrupt Data

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Development (2000)

Floating Point Error - Possibly corrupt Data

Author

Topic

pjsulin
Starting Member

1 Post

Posted - 2006-10-27 : 12:27:44

I'm having a problem that I think is due to corrupt data. Depending on the column I use in my order by clause two problems are occuring.

1. No results are returned and I get this error:
A floating point exception occured in the user process.

2. Results are returned but there are a different number of rows depending on which colums I use in my Order By clause.

Examples
SELECT * FROM SymbolStats
ORDER BY calc_date, symbol

Returns - 12207 rows but only includes one of the 25 dates in the table.

----------

SELECT * from SymbolStats
ORDER BY current_hv

Returns - 0 rows.

----------

SELECT * from SymbolStats
ORDER BY average_hv

Returns - floating point error

With more conditions in the WHERE clause the number of results returned varies greatly.

The fact that different numbers of rows can be returned from the same query only differing in how they are ordered seems like a bug.

Does this sound like corrupt data? If so, what are the best methods for fixing it?

Thanks,
patrick

Kristen
Test

22859 Posts

Posted - 2006-10-28 : 02:47:54

"Does this sound like corrupt data? If so, what are the best methods for fixing it?"

Do you have good backups? If not make a backup NOW!!!!!! before anything else changes and potentially makes the situation worse.

DBCC CHECKDB ('MyDatabaseName') WITH NO_INFOMSGS

will test the database and report if there are any errors.

There are options to "fix" anything that is broken - do NOT use those until you have some advice on any errors that you get!

Kristen

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources