|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Thursday, September 27, 2012 4:24 AM
Points: 253,
Visits: 78
|
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 9:43 AM
Points: 5,101,
Visits: 20,199
|
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 10:33 AM
Points: 10,989,
Visits: 10,529
|
|
The explanation could be better. The question does not involve a float value. By default, the literal value 0.25 is interpreted as a numeric(2,2):
SELECT 0.25 AS col1 INTO #v;
EXECUTE tempdb.sys.sp_columns @table_name = N'#v', @table_owner = N'banana', @table_qualifier = N'tempdb', @column_name = N'col1';
DROP TABLE #v; If the intention has been to show a float, either a float literal or a typed variable could have been used:
SELECT CAST(25e-2 AS datetime);
DECLARE @f float = 25e-2; SELECT CAST(@f AS datetime);
Datetime values are no more "associated" with a float value than they are with any other type that can be implicitly converted (see the conversion table in Books Online - CAST and CONVERT (Transact-SQL)). The internal representation is two integers - one for the number of days from the base date, and one for the number of ticks (1/300th second) since midnight. In fact the second format seems to be 0.003 second time intervals, rounded to 0, 3, or 7 in the third decimal place when used:
DECLARE @dt datetime = '1900-01-02 00:00:00.006'; SELECT @dt; SELECT CONVERT(binary(8), @dt); My biggest concern with this question though, is that it encourages people to be sloppy with types and relies on hidden implicit conversions. As a general rule, try to be explicit about types in T-SQL code.
Paul White SQL Server MVP SQLblog.com @SQL_Kiwi
|
|
|
|
|
SSCrazy Eights
        
Group: General Forum Members
Last Login: Today @ 9:06 AM
Points: 9,367,
Visits: 6,465
|
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 11:02 AM
Points: 5,233,
Visits: 7,031
|
|
Thanks, Paul! You saved me a lot of time by addressing all the points I wanted to address after reading the explanation of this question.
It never ceases to amaze me how many people think datetime data is internally stored as a float. That statement is even being made explicitly in the topic referenced in the explanation of this question. And while this question uses the weaker verb "associate", it will again reinforce that believe for some people.
And now, I am silently hoping that we'll get the same question tomorrow, with the same answer options - but with data type datetime2. <evil grin>
Hugo Kornelis, SQL Server MVP Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Today @ 1:57 PM
Points: 1,875,
Visits: 1,439
|
|
The answer was easy. I also appreciate the discussion from SQL Kiwi.
Thanks IgorMi
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Today @ 1:57 PM
Points: 1,875,
Visits: 1,439
|
|
The answer was easy. I also appreciate the discussion from SQL Kiwi.
Thanks IgorMi
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Today @ 1:57 PM
Points: 1,875,
Visits: 1,439
|
|
The answer was easy. I also appreciate the discussion from SQL Kiwi.
Thanks IgorMi
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 3:48 AM
Points: 3,125,
Visits: 4,311
|
|
Thanks for the simple question. However, as stated by Paul, the idea that DATETIME et al are stored as FLOAT is highly disturbing.
____________________________________________ Space, the final frontier? not any more... All limits henceforth are self-imposed. “libera tute vulgaris ex”
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 10:33 AM
Points: 10,989,
Visits: 10,529
|
|
Hugo Kornelis (5/7/2012) Thanks, Paul! You saved me a lot of time by addressing all the points I wanted to address after reading the explanation of this question. Makes a change! I normally get to the question after you and end up posting the '+1'  I too, look forward to the repeat question based on DATETIME2.
Paul White SQL Server MVP SQLblog.com @SQL_Kiwi
|
|
|
|