Recent PostsRecent Posts Popular TopicsPopular Topics
 Home Search Members Calendar Who's On

 FLOAT vs DECIMAL.. Rate Topic Display Mode Topic Options
Author
 Message
 Posted Thursday, December 20, 2012 5:57 AM
 Mr or Mrs. 500 Group: General Forum Members Last Login: Friday, November 18, 2016 2:29 PM Points: 592, Visits: 1,330
 Hi,I've a table that stores currency amount values and is used in some calculations (vat, discounts, ....).FLOAT, REAL, MONEY and SMALLMONEY can have round issues due to their internal storage method in SQL Server being DECIMAL the only one that hasn't that issue.What's the best mapping from each type to DECIMAL?Should FLOAT and MONEY use the default DECIMAL precision (18) and REAL and SMALLMONEY 9 ?Thanks,Pedro If you need to work better, try working less...
Post #1398932
 Posted Thursday, December 20, 2012 7:27 AM
 SSC Veteran Group: General Forum Members Last Login: Friday, December 4, 2015 9:45 AM Points: 216, Visits: 1,050
 Technically FLOAT, REAL, MONEY and SMALLMONEY all have different ranges, but my standard is just to convert all numeric values of different types, especially values with currency, to Numeric(17,2), and for percents I use Numeric(17,6). Doing this keeps all numeric values standard across the database. Also Numeric and Decimal are equivalents, I just have always used Numeric, but you can use Decimal just the same.Hope this helps ..Sam
Post #1398967
 Posted Thursday, December 20, 2012 8:22 AM
 Hall of Fame Group: General Forum Members Last Login: Saturday, October 24, 2015 2:31 AM Points: 3,158, Visits: 11,771
 samalex (12/20/2012)Technically FLOAT, REAL, MONEY and SMALLMONEY all have different ranges, but my standard is just to convert all numeric values of different types, especially values with currency, to Numeric(17,2), and for percents I use Numeric(17,6). Doing this keeps all numeric values standard across the database. Also Numeric and Decimal are equivalents, I just have always used Numeric, but you can use Decimal just the same.Hope this helps ..SamYou could use NUMERIC(19,2) and NUMERIC(19,6) as your standards, since they use the same amount of storage, 9 bytes, as NUMERIC(17,2) and NUMERIC(17,6).
Post #1399002
 Posted Friday, December 21, 2012 6:33 AM
 SSCertifiable Group: General Forum Members Last Login: Today @ 4:44 PM Points: 7,933, Visits: 14,356
 Comparing FLOAT and REAL to DECIMAL and NUMERIC is not really fair. The former are approximate numeric data types and the latter are exact numeric data types. I am leaving MONEY and SMALLMONEY out of it because those should never be used. For example if you're currently using FLOAT and REAL to sum the precent-segments of a set where the percentage sum should equal 100.00 then if you switch to an exact data type you will start having issues, e.g. coming up with 99.76 or some non-trivial amount away from 100.00. Just throwing it out there, be sure you test to ensure you have chosen the right data type for the job. __________________________________________________________________________________________________There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1399373
 Posted Friday, December 21, 2012 8:12 AM
 Mr or Mrs. 500 Group: General Forum Members Last Login: Friday, November 18, 2016 2:29 PM Points: 592, Visits: 1,330
 opc.three (12/21/2012)Comparing FLOAT and REAL to DECIMAL and NUMERIC is not really fair. The former are approximate numeric data types and the latter are exact numeric data types. I am leaving MONEY and SMALLMONEY out of it because those should never be used. For example if you're currently using FLOAT and REAL to sum the precent-segments of a set where the percentage sum should equal 100.00 then if you switch to an exact data type you will start having issues, e.g. coming up with 99.76 or some non-trivial amount away from 100.00. Just throwing it out there, be sure you test to ensure you have chosen the right data type for the job.My main problem wanting to change to DECIMAL is that we deal with money values and store the value with out VAT, therefore it can be a long decimal value... But cause we store it in float the invoice report, occasionally, gives different values for the total since each line is VALUE + VAT and the total is SUM(VALUE) + VAT and sometimes they are different due to the floating point issue, and also we had 2 reports with different values (cents but different...).Thanks,Pedro If you need to work better, try working less...
Post #1399437
 Posted Friday, December 21, 2012 9:06 AM
 SSCertifiable Group: General Forum Members Last Login: Today @ 4:44 PM Points: 7,933, Visits: 14,356
 For \$ I would recommend an exact numeric data type with the scale you need to satisfy your accounting requirements. __________________________________________________________________________________________________There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1399470

 Permissions