Arithmetic metic overflow error converting decimal to data type numeric while executing a SPROC

Question

0.00/5 (No votes)

See more:

SQL-server-2000

SQL-Server-2005

, +

Hi All,

While executing a SPROC which transfers data from staging DB to Main DB am getting "Arithmetic overflow error converting decimal to data type numeric".

i understand that there is a issue with the scale and precision mismatch, though changing the Main DB scale and precision is not an option for me. Any suggestions please

Posted 6-Oct-12 21:01pm

Shri Wangnekar

Add a Solution

2 solutions

Solution 2

if there is an issue with precision then before in the stored proc, use rounding options to the number of precisions before transferring the data. But still it will result in some data loss. The ideal solution will be still changing the scale and precision in datatype

Posted 6-Oct-12 21:15pm

Santhosh Kumar Jayaraman

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sandip.Nascar · Accepted Answer · 2012-10-06T21:10:00

You are right, this is a scale and precision issue.

Check what decimal scale and precision you have used for the field.
Here is an example
suppose, you declare a data type decimal(8,5)
that means out of 8 digits, 5 will be the decimal point. So, you can have max value 999.
If you have value 1000 or more, you will get the exception.

So, investigate the decimal datatype you have set and the values you are passing.

Hopefully, this solves your problem.

cheers