On Tue, Jun 10, 2008 at 10:34 AM, Jochem van Dieten <[EMAIL PROTECTED]> wrote: > Charlie Griefer wrote: >> Is there any "bottom line" recommendation on using the Money datatype >> in SQL Server? I've googled and found a lot of folks say not to use >> it because of accuracy issues (and of course, the fact that it's >> proprietary), but I haven't seen any that suggest a better >> alternative. >> >> My understanding is that Money is exactly the same as Decimal(19,4)... > > If that is the case, why would you want to use it instead of > Decimal(19,4)? What value does it add to your application?
There are some people here who suggest that it makes the database more self documenting, and I don't disagree with that... but if there are indeed accuracy issues I think that outweighs the self-documenting aspect :) What I'm not fully understanding is if those same accuracy issues exist with Decimal(19,4). And if they do, is the solution to just be judicious in the use of Round() functions? or is using Float the "preferred" option. Thanks, Charlie -- A byte walks into a bar and orders a pint. Bartender asks him "What's wrong?" Byte says "Parity error." Bartender nods and says "Yeah, I thought you looked a bit off." ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307189 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
