Comments on: SQL SERVER – Saturday Fun Puzzle with SQL Server DATETIME2 and CAST http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/ Personal Notes of Pinal Dave Fri, 17 May 2013 15:26:57 +0000 hourly 1 http://wordpress.com/ By: SQL SERVER – Display Datetime in Specific Format – SQL in Sixty Seconds #033 – Video « SQL Server Journey with SQL Authority http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-377772 Wed, 21 Nov 2012 01:30:53 +0000 http://blog.sqlauthority.com/?p=18763#comment-377772 [...] Saturday Fun Puzzle with SQL Server DATETIME2 and CAST [...]

]]> By: Tim http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-352781 Mon, 24 Sep 2012 21:19:59 +0000 http://blog.sqlauthority.com/?p=18763#comment-352781 It isn’t a direct issue of varchar. I think SQL performis an internal convert(varchar(100),getdate). Since a style was not specified it is applying the default (100) which is Mon dd yyyy hh:mmAM. This excludes seconds and milliseconds in the text string. If we used convert(varchar(100),getdate(),113) our answers would be the same. Unfortunately Cast is ANSI 92 standard while Convert is not.

]]> By: pinaldave http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-286202 Sat, 19 May 2012 17:25:41 +0000 http://blog.sqlauthority.com/?p=18763#comment-286202 Great observation!

]]> By: pinaldave http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-286200 Sat, 19 May 2012 17:25:03 +0000 http://blog.sqlauthority.com/?p=18763#comment-286200 Super!

]]> By: pinaldave http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-286199 Sat, 19 May 2012 17:24:43 +0000 http://blog.sqlauthority.com/?p=18763#comment-286199 Excellent Point!

]]> By: Rajan http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-286053 Sat, 19 May 2012 07:55:52 +0000 http://blog.sqlauthority.com/?p=18763#comment-286053 Varchar may not provide values in seconds, but datetime2 specifically provides values in seconds and milliseconds.

Even after converting Varchar into Datetime2, it will not provide the same value as of datetime2.

]]> By: Purna Magum http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-286034 Sat, 19 May 2012 06:59:33 +0000 http://blog.sqlauthority.com/?p=18763#comment-286034 As Q1 & Q2′s of field data types are same that’s the reason result set is same.
In Q3 then DT1C field’s data type is nvarchar and type casting to datetime2 type that’s the reason it is converting like this

]]> By: Anil Sharma http://blog.sqlauthority.com/2012/05/19/sql-server-saturday-fun-puzzle-with-sql-server-datetime2-and-cast/#comment-285941 Sat, 19 May 2012 02:16:20 +0000 http://blog.sqlauthority.com/?p=18763#comment-285941 Q1 and Q2 have same answer becaz. they have same field type.
Due to Cast Function Varchar is converted to DateTime Thats why we are seeing the difference.

]]>