-3

Possible Duplicate:
What is the significance of 1/1/1753 in SQL Server?

In SqlDateTime.MinValue is 1753

Why the last two digits are 53? Why it is not rounded to 1700?

Anyone know the reason behind this? :)

edit: I corrected the question. :)

Community
  • 1
  • 1
Murat
  • 349
  • 2
  • 4
  • 11
  • 7
    http://stackoverflow.com/questions/3310569/what-is-the-significance-of-1-1-1753-in-sql-server – Guillaume Sep 16 '11 at 08:53
  • 2
    [It is not 1753](http://msdn.microsoft.com/en-us/library/system.datetime.minvalue.aspx) -- where did you get that value from? – Jon Sep 16 '11 at 08:53
  • 1
    I think its sql min datetime value .. [`yes Indeed`](http://msdn.microsoft.com/en-us/library/system.data.sqltypes.sqldatetime.minvalue.aspx) – V4Vendetta Sep 16 '11 at 08:55
  • @Jon, I believe that's the minimum date for the datetime type in SQL server. Not to be confused with the DateTime type in the .NET framework as you mention. – Christophe Geers Sep 16 '11 at 08:56
  • @ChristopheGeers: I read (and upvoted) the answer Guillaume links to, so now I know. But the question is totally misleading. – Jon Sep 16 '11 at 08:57

1 Answers1

11

DateTime.MinValue is 01/01/0001 00:00:00.

As for why SqlDateTime.MinValue is in 1753, that's answered here: SqlDateTime.MinValue != DateTime.MinValue, why? and here: What is the significance of 1/1/1753 in SQL Server?

Community
  • 1
  • 1
David Heffernan
  • 601,492
  • 42
  • 1,072
  • 1,490