Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.
convert to datetime
How can I convert the string '31.5.2016 00:00:00' to date time.
If I do
SELECT CONVERT(datetime,'31.5.201
I get the error:
The conversion of a varchar data type to a datetime data type resulted in an out -of-range value.
If I do
SELECT CONVERT(datetime,'31.5.201
I get the error:
The conversion of a varchar data type to a datetime data type resulted in an out -of-range value.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
If this is SQL-Server, I think you are missing last parameter. CONVERT has 3 parameters, and the third specifies the format.
https://msdn.microsoft.com/en-us/library/ms187928%28v=sql.120%29.aspx
https://msdn.microsoft.com/en-us/library/ms187928%28v=sql.120%29.aspx
Yes, it is optional but I would recommend to use it in order to "explain" to the computer what kind of format are you using on the string.
Just CAST it. CAST is more flexible in that it will accept any valid format without you having to provide a specific code for it:
SELECT CAST('31.5.2016 00:00:00' AS datetime)
SELECT CAST('31.5.2016 00:00:00' AS datetime)
Yes, but the problem is that some dates as 3/2/2015 could be read as febrary the 3th of 2015 or as march the 2nd of 2015. So I think it is a good idea to provide which format are you using to avoid ambiguosities
Yes, but if you relay of local date settings, what happens when you run the program on another computer? What if you migrate the server?
?? Presumably if you're storing dates as strings in a local table, they will be stored in the local format.
If you're entering dates yourself as literals, you should always use format:
'YYYYMMDD hh:mm:ss' --hh=24hr
which works with any settings so you don't need a format code.
If you're entering dates yourself as literals, you should always use format:
'YYYYMMDD hh:mm:ss' --hh=24hr
which works with any settings so you don't need a format code.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
SELECT CONVERT(datetime,'2016-05-
ISO 8601 is always a good idea as it's easy to remember (largest unit to smallest), easy to read, and avoids any confusion over non-US/US date formatting (i.e. day before month vs month before day).