I don't know if anyone else has experiencing this issue before
I have DateTime Data in a MsSQl table but when displaying the same data in Navison 2013, it is displaying the time wrongly.
2018-12-14 08:20:22.000 is being displayed as 14-12-18 11:20:22 AM
Any suggestions ?
Thanks in Advance
The time stored in the SQL database will be stored in UTC. However, since you're based in Kenya (I assume from your profile), your time zone is UTC+3. Navision (Dynamics NAV) automatically converts UTC time into your local time zone.
So if you're writing to the database directly without going through Navision you should use UTC time to save the time.
Related
Is there a function in SQL Server that will convert a DateTime saved as UTC time to the local time? The problem is that I have times saved as UTC times, and I used to calculate time zone offset as
select #tzoffset = datediff(mi,SYSDATETIMEOFFSET(),SYSDATETIME())
and adding that to my UTC times, which worked fine until daylight saving came.
As that selects the current time zone offset, the calculation is invalid for pre-DST values.
As the dates are rendered in ASP.NET web form, I have worked around the issue by rendering the dates as TimeZoneInfo.ConvertTimeFromUtc((DateTime)Eval("maxtime"), TimeZoneInfo.Local), which works automagically.
Is there something similarly elegant in T-SQL?
It is not that simple. Read this http://blogs.msdn.com/b/bartd/archive/2009/03/31/the-death-of-datetime.aspx
I have SL 5 app with a form which has a field for Date.
I set the default date for this field in code like:
MyDate = System.DateTime.Today;
Or
MyDate = System.DateTime.Now.Date;
then submit the data with WCF Ria Service to save the data into database.
Problem is: if time zone on user client computer and Web server are different, the data of date would be saved with different value.
For example, today is Jan-03-2013, when I save the data from the form, in database, the data is saved as something like Jan-02-2013 23:00:00., not Jan-03-2013 00:00:00.
How to fix this problem?
you could try using
MyDate = DateTime.UtcNow
which would return utc time to the server then you can either store all datetimes as utc or manipulate it before saving to the the db (so it would be saved as server's local time)
In addition to timezone differences, there can be also real date value difference between client and server.
For that reason I think you should always get the date from server each time or you should ger the time at the application startup from both the client and server and find the the difference interval. Then you should calculate server datetime by adding the difference to the local date value.
For the timezone differences, also you should alway work in UTC format bu you should show the value to the user as local timezone format of course.
I am working with Silverlight and I am getting a problem. In my Database I have stored some dates with a format like this yyyy/mm/dd 00:00:00, which means that I store only the year, month and day, getting the time to 00:00:00.
When the client performs an action and sends to the server I get the DateTime.Today which will keep the format of my database date, but when it is sendind I get yyyy/mm/dd 22:00:00, so when my server side function gets the date, it will return no values from the database.
How can I fix this to get the correct datetime?
Thank you
Use UTC times to make sure you don't run into timezone issues.
You can see if the DateTime is UTC or local based by checking the Kind property, and you can get the current UTC time by DateTime.UtcNow.
DateTime structure is very prone to DST, timezones and cultures when serialising it.
are you serialising it at client side before push it ? what is the difference between client and server timezones ?
I would suggest that you try and consume DateTime.UtcNow and then serialise the data. i prefer to serialise using Invariant culture
HTH
In addition to storing UTC time in the database, you can hard set the time to 12:00:00 for all date values by using the Date property of the DateTime class.
DateTime.UtcNow.Date
You can present the date to the user in their local timezone using the ToLocalTime method:
DateTime.ToLocalTime().Date
I'm sure every database engine has a similar function, but the SQL Server function to get UTC date is (surprisingly enough):
GETUTCDATE()
I hope this helps.
I transfer data from one SQL Server to another using SELECT * INTO .... statement (in Management Studio). Both databases have different timezone settings.
Is it possible to adjust all date/time fields to different timezone automatically? Maybe some query parameters or connection settings?
Since you are on SQL Server 2008, you could use the built-in functionality of the DATETIMEOFFSET datatype, and the SWITCHOFFSET function.
You could do something like:
INSERT INTO dbo.YourTargetTable( ...... )
SELECT
SWITCHOFFSET(TODATETIMEOFFSET(YourSourceTime, '+04:00'), '-09:00'),
.......
TODATETIMEOFFSET converts your "regular" date without any timezone information into a DATETIMEOFFSET type with a time zone (of your source location), and then you can apply a SWITCHOFFSET call to that value to "switch" your date/time to your target location's time zone.
This can be done in the scope of the INSERT....SELECT statement - no separate "row-by-row" updating necessary.
I think this will be helpful, please follow the link:
Effectively Converting dates between UTC and Local (ie. PST) time in SQL 2005
Shortly, you do need to build time zone and DST tables to get some help with time zones.
Thanks
Is there any way to prevent Silverlight/RIA Services from converting a datetime object on the wire?
Right now, I see datetimes set to 'Local' or 'Unspecified' being converted to the local time of the server when they are sent over the wire.
For example:
The client and server are both in UTC -04:00:00.
I use DateTime.Today (kind is either Local or Unspecified, it doesn't make a difference) on the Silverlight client. I see 23/08/2010 00:00:00.
I submit my changes and watch the data go over the wire. The field is expressed at 23/08/2010 00:00:00 (-04:00:00).
Great. Now I change my client to be in UTC +12:00:00
I use DateTime.Today on the client and now I see 24/08/2010 00:00:00.
HOWEVER - I submit my changes and watch the data again. Now I see 23/08/2010 08:00:00 (-04:00:00).
So it is apparent that the serializer is converting to the local time of the server, which I do not want. The value I want in the DB is 24/08/2010 00:00:00.
Using UTC is not a great option for this field as the database is part of our legacy application and the column contains invariant dates at this time. I don't want to start inserting UTC datetimes alongside the existing data.
Any ideas?
Thanks in advance
If I create the DateTime like this, it works:
new DateTime(DateTime.Now.Ticks, DateTimeKind.Unspecified).Date;