I'm having a pretty common problem but my usual solution isn't working. I've got a highly precise value stored as a character in a staging table. When I push it to it's final destination, a column with data type numeric(38,38), it fails. I thought it was because of the negative sign, but when I get rid of it, I still have an issue. I've got the numeric column maxed out but I'm still getting the following error:
Arithmetic overflow error converting nvarchar to data type numeric.
Normally I just convert to float but that isn't working. Besides which, I want to retain the precision of the value and float appears to take that away.
What am I missing here?
DECLARE #Value NVARCHAR(255) = '-1.000000000000000'
SELECT CAST(#Value AS numeric(38,38))
DECLARE #Value NVARCHAR(255) = '-1.000000000000000'
SELECT CAST(CAST(#Value AS FLOAT) AS numeric(38,38))
CLARIFICATION:
numeric(38,38) are absurd parameters and were only used for testing and as an example for this question. The original column was set to numeric(16,15) which worked more than 99% of the time on a dataset of millions of records and thus didn't flag as an issue.
numeric(38,38) is a numeric value of 38 digits, 38 of which are after the decimal. Because of this, any number greater than 1 or less than -1 (has 1 or more digits to the left of the decimal) will overflow. You need to account for the maximum number of digits that may occur to both the left and the right of the decimal.
1.00001 would be numeric(6,5) with 6 digits, 5 of which are on the right of the decimal, 1 of which is on the left.
10.00001 would be numeric(7,5) with 7 digits, 5 of which are on the right of the decimal, 2 of which are on the left.
Related
We are doing some validation of data which has been migrated from one SQL Server to another SQL Server. One of the things that we are validating is that some numeric data has been transferred properly. The numeric data is stored as a float datatype in the new system.
We are aware that there are a number of issues with float datatypes, that exact numeric accuracy is not guaranteed, and that one cannot use exact equality comparisons with float data. We don't have control over the database schemas nor data typing and those are separate issues.
What we are trying to do in this specific case is verify that some ratio values were transferred properly. One of the specific data validation rules is that all ratios should be transferred with no more than 4 digits to the right of the decimal point.
So, for example, valid ratios would look like:
.7542
1.5423
Invalid ratios would be:
.12399794301
12.1209377
What we would like to do is count the number of digits to the right of the decimal point and find all cases where the float values have more than four digits to the right of it. We've been using the SUBSTRING, LEN, STR, and a couple of other functions to achieve this, and I am sure it would work if we had numeric fields typed as decimal which we were casting to char.
However, what we have found when attempting to convert a float to a char value is that SQL Server seems to always convert to decimal in between. For example, the field in question shows this value when queried in SQL Server Enterprise Manager:
1.4667
Attempting to convert to a string using the recommended function for SQL Server:
LTRIM(RTRIM(STR(field_name, 22, 17)))
Returns this value:
1.4666999999999999
The value which I would expect if SQL Server were directly converting from float to char (which we could then trim trailing zeroes from):
1.4667000000000000
Is there any way in SQL Server to convert directly from a float to a char without going through what appears to be an intermediate conversion to decimal along the way? We also tried the CAST and CONVERT functions and received similar results to the STR function.
SQL Server Version involved: SQL Server 2012 SP2
Thank you.
Your validation rule seems to be misguided.
An SQL Server FLOAT, or FLOAT(53), is stored internally as a 64-bit floating-point number according to the IEEE 754 standard, with 53 bits of mantissa ("value") plus an exponent. Those 53 binary digits correspond to approximately 15 decimal digits.
Floating-point numbers have limited precision, which does not mean that they are "fuzzy" or inexact in themselves, but that not all numbers can be exactly represented, and instead have to be represented using another number.
For example, there is no exact representation for your 1.4667, and it will instead be stored as a binary floating-point number that (exactly) corresponds to the decimal number 1.466699999999999892708046900224871933460235595703125. Correctly rounded to 16 decimal places, that is 1.4666999999999999, which is precisely what you got.
Since the "exact character representation of the float value that is in SQL Server" is 1.466699999999999892708046900224871933460235595703125, the validation rule of "no more than 4 digits to the right of the decimal point" is clearly flawed, at least if you apply it to the "exact character representation".
What you might be able to do, however, is to round the stored number to fewer decimal places, so that the small error at the end of the decimals is hidden. Converting to a character representation rounded to 15 instead of 16 places (remember those "15 decimal digits" mentioned at the beginning?) will give you 1.466700000000000, and then you can check that all decimals after the first four are zeroes.
You can try using cast to varchar.
select case when
len(
substring(cast(col as varchar(100))
,charindex('.',cast(col as varchar(100)))+1
,len(cast(col as varchar(100)))
)
) = 4
then 'true' else 'false' end
from tablename
where charindex('.',cast(col as varchar(100))) > 0
For this particular number, don't use STR(), and use a convert or cast to varchar. But, in general, you will always have precision issues when storing in float... it's the nature of the storage of that datatype. The best you can do is normalize to a NUMERIC type and compare with threshold ranges (+/- .0001, for example). See the following for a breakdown of how the different conversions work:
declare #float float = 1.4667
select #float,
convert(numeric(18,4), #float),
convert(nvarchar(20), #float),
convert(nvarchar(20), convert(numeric(18,4), #float)),
str(#float, 22, 17),
str(convert(numeric(18,4), #float)),
convert(nvarchar(20), convert(numeric(18,4), #float))
Instead of casting to a VarChar you might try this: cast to a decimal with 4 fractional digits and check if it's the same value as before.
case when field_name <> convert(numeric(38,4), field_name)
then 1
else 0
end
The issue you have here is that float is an approximate number data type with an accuracy of about seven digits. That means it approaches the value while using less storage than a decimal / numeric. That's why you don't use float for values that require exact precision.
Check this example:
DECLARE #t TABLE (
col FLOAT
)
INSERT into #t (col)
VALUES (1.4666999999999999)
,(1.4667)
,(1.12399794301)
,(12.1209377);
SELECT col
, CONVERT(NVARCHAR(MAX),col) AS chr
, CAST(col as VARBINARY) AS bin
, LTRIM(RTRIM(STR(col, 22, 17))) AS rec
FROM #t
As you see the float 1.4666999999999999 binary equals 1.4667. For your stated needs I think this query would fit:
SELECT col
, RIGHT(CONVERT(NVARCHAR(MAX),col), LEN(CONVERT(NVARCHAR(MAX),col)) - CHARINDEX('.',CONVERT(NVARCHAR(MAX),col))) AS prec
from #t
I am using SQL Server 2008 R2 and I want to find rounding up and down values with specific decimal points as shown as below:
For Example:
If my Value is 1.27845 and I want the answer with 2 decimal places then my answer should be
Rounding UP: 1.28
Rounding Down: 1.27
If my Value is 33.33333 and I want the answer with 2 decimal places then my answer should be
Rounding UP: 33.34
Rounding Down: 33.33
If my Value is 1.27845 and I want the answer with 3 decimal places then my answer should be
Rounding UP: 1.279
Rounding Down: 1.278
If my Value is 33.33333 and I want the answer with 3 decimal places then my answer should be
Rounding UP: 33.334
Rounding Down: 33.333
I want common solution for all cases.
Thanks...
You could could use the following "offset" together with FLOOR and CEILING
DECLARE
#digit int = 2,
#value decimal(10,5)=1.27845
DECLARE
#calc_scale int = POWER(10,#digit)
SELECT
CAST(FLOOR (#value * #calc_scale)/#calc_scale AS DECIMAL(10,5)) as down,
CAST(CEILING (#value * #calc_scale)/#calc_scale AS DECIMAL(10,5)) as up
However, the target data type would always be as specified in the query (e.g. a precision edit: scale of 5 in the example above).
You can't change the number of digits in the output dynamically, since this scale depends on the data type of the variable. You could mess around with a conversion to a VARCHAR data type and trim the unwanted digits, but I strongly vote against it.
If you need to display only the significant number of digits, I recommend to trim it at the application layer.
I Couldn'd add my code keep on getting this error "an error occurred submitting the answer" so added as picture
I need help from SQL experts. I'm trying to get data with 4 decimal places. I'm doing some calculation on type "money". However, the calculation doesn't round to mine liking.
Below is an example with regular numbers and the same values of money type.
DECLARE #MaxAmt money
DECLARE #MinAmt money
SET #MaxAmt = 207998693.55
SET #MinAmt = 20799442.35
SELECT
((207998693.55 - 20799442.35) / 2 + 20799442.35) / 24 AS Col1,
((#MaxAmt - #MinAmt) / 2 + #MinAmt) / 24 AS Col2
Col1 displays value equals to 4766627.831250000
While Col2 has value 4766627.8312.
My goal is to display only 4 decimal digits but it should be round correctly. I would expect 4766627.8313 value.
Which would displayed after following casting.
SELECT CAST(((207998693.55 - 20799442.35) / 2 + 20799442.35) / 24 AS DECIMAL(12,4))
But when I deal with money type my value after a decimal is .8312 instead of .8313
The most likely explanation for this behavior is that the Money type is using what's known as Banker's Rounding (a review of that page should reveal the likely reasons this was chosen).
Skimming through the documentation, there doesn't seem to be anything 'built in' to change this - you'll likely need to cast to DECIMAL first, explicitly, if you want to perform this in SQL itself. (Alternatives include pulling at least some of the calculation out to your application layer, if necessary, or writing a stored procedure).
I have a column X which is full of floats with decimals places ranging from 0 (no decimals) to 6 (maximum). I can count on the fact that there are no floats with greater than 6 decimal places. Given that, how do I make a new column such that it tells me how many digits come after the decimal?
I have seen some threads suggesting that I use CAST to convert the float to a string, then parse the string to count the length of the string that comes after the decimal. Is this the best way to go?
You can use something like this:
declare #v sql_variant
set #v=0.1242311
select SQL_VARIANT_PROPERTY(#v, 'Scale') as Scale
This will return 7.
I tried to make the above query work with a float column but couldn't get it working as expected. It only works with a sql_variant column as you can see here: http://sqlfiddle.com/#!6/5c62c/2
So, I proceeded to find another way and building upon this answer, I got this:
SELECT value,
LEN(
CAST(
CAST(
REVERSE(
CONVERT(VARCHAR(50), value, 128)
) AS float
) AS bigint
)
) as Decimals
FROM Numbers
Here's a SQL Fiddle to test this out: http://sqlfiddle.com/#!6/23d4f/29
To account for that little quirk, here's a modified version that will handle the case when the float value has no decimal part:
SELECT value,
Decimals = CASE Charindex('.', value)
WHEN 0 THEN 0
ELSE
Len (
Cast(
Cast(
Reverse(CONVERT(VARCHAR(50), value, 128)) AS FLOAT
) AS BIGINT
)
)
END
FROM numbers
Here's the accompanying SQL Fiddle: http://sqlfiddle.com/#!6/10d54/11
This thread is also using CAST, but I found the answer interesting:
http://www.sqlservercentral.com/Forums/Topic314390-8-1.aspx
DECLARE #Places INT
SELECT TOP 1000000 #Places = FLOOR(LOG10(REVERSE(ABS(SomeNumber)+1)))+1
FROM dbo.BigTest
and in ORACLE:
SELECT FLOOR(LOG(10,REVERSE(CAST(ABS(.56544)+1 as varchar(50))))) + 1 from DUAL
A float is just representing a real number. There is no meaning to the number of decimal places of a real number. In particular the real number 3 can have six decimal places, 3.000000, it's just that all the decimal places are zero.
You may have a display conversion which is not showing the right most zero values in the decimal.
Note also that the reason there is a maximum of 6 decimal places is that the seventh is imprecise, so the display conversion will not commit to a seventh decimal place value.
Also note that floats are stored in binary, and they actually have binary places to the right of a binary point. The decimal display is an approximation of the binary rational in the float storage which is in turn an approximation of a real number.
So the point is, there really is no sense of how many decimal places a float value has. If you do the conversion to a string (say using the CAST) you could count the decimal places. That really would be the best approach for what you are trying to do.
I answered this before, but I can tell from the comments that it's a little unclear. Over time I found a better way to express this.
Consider pi as
(a) 3.141592653590
This shows pi as 11 decimal places. However this was rounded to 12 decimal places, as pi, to 14 digits is
(b) 3.1415926535897932
A computer or database stores values in binary. For a single precision float, pi would be stored as
(c) 3.141592739105224609375
This is actually rounded up to the closest value that a single precision can store, just as we rounded in (a). The next lowest number a single precision can store is
(d) 3.141592502593994140625
So, when you are trying to count the number of decimal places, you are trying to find how many decimal places, after which all remaining decimals would be zero. However, since the number may need to be rounded to store it, it does not represent the correct value.
Numbers also introduce rounding error as mathematical operations are done, including converting from decimal to binary when inputting the number, and converting from binary to decimal when displaying the value.
You cannot reliably find the number of decimal places a number in a database has, because it is approximated to round it to store in a limited amount of storage. The difference between the real value, or even the exact binary value in the database will be rounded to represent it in decimal. There could always be more decimal digits which are missing from rounding, so you don't know when the zeros would have no more non-zero digits following it.
Solution for Oracle but you got the idea. trunc() removes decimal part in Oracle.
select *
from your_table
where (your_field*1000000 - trunc(your_field*1000000)) <> 0;
The idea of the query: Will there be any decimals left after you multiply by 1 000 000.
Another way I found is
SELECT 1.110000 , LEN(PARSENAME(Cast(1.110000 as float),1)) AS Count_AFTER_DECIMAL
I've noticed that Kshitij Manvelikar's answer has a bug. If there are no decimal places, instead of returning 0, it returns the total number of characters in the number.
So improving upon it:
Case When (SomeNumber = Cast(SomeNumber As Integer)) Then 0 Else LEN(PARSENAME(Cast(SomeNumber as float),1)) End
Here's another Oracle example. As I always warn non-Oracle users before they start screaming at me and downvoting etc... the SUBSTRING and INSTRING are ANSI SQL standard functions and can be used in any SQL. The Dual table can be replaced with any other table or created. Here's the link to SQL SERVER blog whre i copied dual table code from: http://blog.sqlauthority.com/2010/07/20/sql-server-select-from-dual-dual-equivalent/
CREATE TABLE DUAL
(
DUMMY VARCHAR(1)
)
GO
INSERT INTO DUAL (DUMMY)
VALUES ('X')
GO
The length after dot or decimal place is returned by this query.
The str can be converted to_number(str) if required. You can also get the length of the string before dot-decimal place - change code to LENGTH(SUBSTR(str, 1, dot_pos))-1 and remove +1 in INSTR part:
SELECT str, LENGTH(SUBSTR(str, dot_pos)) str_length_after_dot FROM
(
SELECT '000.000789' as str
, INSTR('000.000789', '.')+1 dot_pos
FROM dual
)
/
SQL>
STR STR_LENGTH_AFTER_DOT
----------------------------------
000.000789 6
You already have answers and examples about casting etc...
This question asks of regular SQL, but I needed a solution for SQLite. SQLite has neither a log10 function, nor a reverse string function builtin, so most of the answers here don't work. My solution is similar to Art's answer, and as a matter of fact, similar to what phan describes in the question body. It works by converting the floating point value (in SQLite, a "REAL" value) to text, and then counting the caracters after a decimal point.
For a column named "Column" from a table named "Table", the following query will produce a the count of each row's decimal places:
select
length(
substr(
cast(Column as text),
instr(cast(Column as text), '.')+1
)
) as "Column-precision" from "Table";
The code will cast the column as text, then get the index of a period (.) in the text, and fetch the substring from that point on to the end of the text. Then, it calculates the length of the result.
Remember to limit 100 if you don't want it to run for the entire table!
It's not a perfect solution; for example, it considers "10.0" as having 1 decimal place, even if it's only a 0. However, this is actually what I needed, so it wasn't a concern to me.
Hopefully this is useful to someone :)
Probably doesn't work well for floats, but I used this approach as a quick and dirty way to find number of significant decimal places in a decimal type in SQL Server. Last parameter of round function if not 0 indicates to truncate rather than round.
CASE
WHEN col = round(col, 1, 1) THEN 1
WHEN col = round(col, 2, 1) THEN 2
WHEN col = round(col, 3, 1) THEN 3
...
ELSE null END
I have a column declared as decimal(4,4). Currently it stores 0.0400 as the value. Now I need to update the value stored from 0.0400 to 9.95.I used the following query :
Update <tablename>
set <columnname>= 9.95
where <condition>
When I try to execute, I get the following error :
Arithmetic overflow error converting numeric to data type numeric.
The statement has been terminated.
Kindly help.
Defining a column as decimal(4,4) is the equivalent of saying
I will have 4 digits in total, of which 4 come after the decimal point
To represent 9.95, you'd need to store it as 9.9500 to satisfy the '4 decimal places' condition. But this now exceeds the 'max 4 digits' condition and so can't be converted.
You'd need at least decimal(5, 4) to store 9.95 as a decimal in this way.
If you write decimal(4,4), what the database hears is:
There are four digits total
All four of them are behind the decimal separator
So a decimal(4,4) can store the range 0.0000 to 0.9999 (and its negative equivalent). But 9.95 is outside that range, so it will return an error.
I had similar issue few years ago, here is my understanding.
Decimal(TotalDigitsIncludingDecimal,DecimalPlaces)
Eg: Value = 50.05 declare Decimal(4,2)
Eg: Value = 5000.0005 declare Decimal(8,4)
Decimal(6,2) means:
At most 4 digits to the left of the decimal point, since you can have 2 to the right of the decimal point. (even if you don't see them, or use them)
It is VERY wrong to say "you can have 6 digits total".
12345 is less than 6 digits total. But it'll overflow.
I'm not sure why SQL didn't just make it "Decimal(left, right)" and you would instantly see the limits you can store there.