September 13, 2010 at 2:07 pm
Couple of days back, we migrated a database from SQL Server 2000 to SQL server 2005.
Today, the ETL team is complaining that they are getting this error "Arithmetic overflow error converting float to data type numeric. " when they are running an update statement.
Was migration the culprit by any chance or is it something else?
September 13, 2010 at 2:53 pm
I would doubt it. I'd look more for a funky piece of data. If you can, find out what the numeric settings they have are, then go to the source data and look for a number with a higher value then the left side of the numeric can hold.
IE: If you're numeric (6,2), which is 4 left then 2 right, and your float is 12345.01234568798756231... That will break with this error.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 13, 2010 at 3:06 pm
An off the wall guess ... have you checked your DB option settings
(DBCC USEROPTIONS) to determine if arithabort is set?
September 13, 2010 at 3:11 pm
I think this issue doesn't have to do anything with the migration.
Thank You,
Best Regards,
SQLBuddy
September 13, 2010 at 4:06 pm
You may be right because it runs fine when I run it on Dev box which has SQL 2005 on it.
Could you please guide me how do I set this option? And also, would this affect other queries by any chance?
Thanks,
Sunny.
September 14, 2010 at 7:40 am
sunny.tjk
To learn more about these options and their effects read this:
http://technet.microsoft.com/en-us/library/ms190356(SQL.90).aspx
How to set the option(s) read this:
http://technet.microsoft.com/en-us/library/ms190306(SQL.90).aspx
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply