<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 - General
»
SqlDateTime overflow
14 posts, Page 2 of 2
««
1
2
SqlDateTime overflow
Rate Topic
Display Mode
Topic Options
Author
Message
jerry-621596
jerry-621596
Posted Wednesday, January 09, 2013 12:56 PM
Old Hand
Group: General Forum Members
Last Login: Monday, May 13, 2013 4:18 PM
Points: 363,
Visits: 574
I use .NET 4.0 and they did not update the date range limits in the libraries to match the new range in SQL Sever. I will have to wait until I get home, but will try to find a workaround I came up with and post it here for you.
This was a one week research project for me so if I can find my fix it could save you a ton of time.
Post #1404960
lonhanner
lonhanner
Posted Wednesday, January 09, 2013 2:47 PM
SSC Rookie
Group: General Forum Members
Last Login: Friday, February 22, 2013 11:14 AM
Points: 39,
Visits: 141
Thanks so very much. It would look like MS would fix this.
I set my dates fields to "date" in sql and my time to "time(4)
Post #1405026
jerry-621596
jerry-621596
Posted Wednesday, January 09, 2013 3:00 PM
Old Hand
Group: General Forum Members
Last Login: Monday, May 13, 2013 4:18 PM
Points: 363,
Visits: 574
Different dev teams I guess. Not very efficient.
Post #1405034
jerry-621596
jerry-621596
Posted Wednesday, January 09, 2013 8:13 PM
Old Hand
Group: General Forum Members
Last Login: Monday, May 13, 2013 4:18 PM
Points: 363,
Visits: 574
OK, just so everyone understands, this is not a SQL problem. The .NET Framework has a special data type for SQL databases in System.Data.SqlTypes.SqlDateTime. For some really silly reason, this data type's MinValue method has not been expanded to use the new minimum date. Probably because no one at Microsoft even thought about adding a SqlDateTime2 type, or any of the others like SqlDate and SqlTime.
What I had to do is find the code in my data access library that used SqlDateTime.MinValue to check dates before sending them to the database and changed it to use DateTime.MinValue. That will use the proper minimum date.
Do be sure and use DateTime2 in SQL or the database will be the next thing that will throw an error.
Hope this helps.
Post #1405138
« Prev Topic
|
Next Topic »
14 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
