Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««23456»»»

How well do you know MAX? Expand / Collapse
Author
Message
Posted Friday, August 5, 2011 10:14 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, July 25, 2014 9:09 AM
Points: 395, Visits: 168

Great question!

Thanks
Post #1155200
Posted Friday, August 5, 2011 10:23 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 2:27 PM
Points: 21,657, Visits: 15,324
thanks for the ¿



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1155208
Posted Friday, August 5, 2011 10:29 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 8:36 AM
Points: 3,918, Visits: 3,638
I thought this question was about using approximate data types so got it right for the wrong reason.
Post #1155215
Posted Friday, August 5, 2011 10:47 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, October 21, 2013 11:43 PM
Points: 945, Visits: 1,234
Excellent question and indeed a brain teaser!

Amol Naik
Post #1155226
Posted Friday, August 5, 2011 10:51 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, August 28, 2014 8:53 PM
Points: 1,521, Visits: 3,039
Cliff Jones (8/5/2011)
I thought this question was about using approximate data types so got it right for the wrong reason.

I would hope that most viewers of this understand that the FLOAT datatype is generally not a good idea for monetary values, but let's say it to be sure.
Post #1155228
Posted Friday, August 5, 2011 11:39 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Saturday, August 23, 2014 8:01 PM
Points: 1,364, Visits: 1,056
This has been one of the best weeks for QOTD that I can remember, and today's question was like the frosting on the cake! Thanks to all of you who put the effort into submitting questions to educate and amuse us.
Post #1155267
Posted Friday, August 5, 2011 11:53 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Today @ 5:07 AM
Points: 8,745, Visits: 9,293
john.arnott (8/5/2011)
Cliff Jones (8/5/2011)
I thought this question was about using approximate data types so got it right for the wrong reason.

I would hope that most viewers of this understand that the FLOAT datatype is generally not a good idea for monetary values, but let's say it to be sure.

I would hope that most people realise that in applications where monetary values range from 0.01 units to 90071992547409.92 units (something over nine hundred million million units), and no greater accuracy than two places after the point is needed, float (which is a synonym for float(53)) is usually far more storage efficient and usually far mor eperformance efficient than any decimal or money type, and no less accurate. Let's hope people also realise that that covers the vast majority of applications involving monetary values.

But. let's say it, just to be sure that the anti-float myth invented years ago by Cobol advocates is not carried over unchallenged into modern times.


Tom
Post #1155281
Posted Friday, August 5, 2011 2:12 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232, Visits: 1,046
Tom.Thomson (8/5/2011)
john.arnott (8/5/2011)
Cliff Jones (8/5/2011)
I thought this question was about using approximate data types so got it right for the wrong reason.

I would hope that most viewers of this understand that the FLOAT datatype is generally not a good idea for monetary values, but let's say it to be sure.

I would hope that most people realise that in applications where monetary values range from 0.01 units to 90071992547409.92 units (something over nine hundred million million units), and no greater accuracy than two places after the point is needed, float (which is a synonym for float(53)) is usually far more storage efficient and usually far mor eperformance efficient than any decimal or money type, and no less accurate. Let's hope people also realise that that covers the vast majority of applications involving monetary values.

But. let's say it, just to be sure that the anti-float myth invented years ago by Cobol advocates is not carried over unchallenged into modern times.


Nice one TOM... FLOATing is better than SINking...

"Life is tough, it's tougher if your are stupid and use COBOL"
-RGB develeopment team motto
Post #1155347
Posted Friday, August 5, 2011 2:14 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232, Visits: 1,046
Great Question. Saw that your NOT IN had only one result and NOT two right away.
Post #1155348
Posted Friday, August 5, 2011 8:51 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Saturday, August 30, 2014 4:20 PM
Points: 11,194, Visits: 11,142
You almost had me



Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #1155473
« Prev Topic | Next Topic »

Add to briefcase «««23456»»»

Permissions Expand / Collapse