How to solve datetime conversion errors

Question

1.00/5 (1 vote)

See more:

I want to convert a nvarchar(250) to datetime in a database.

Actually I have converted access database into sql in access they mention INV

Date datatype as text so it is converted into nvarchar(250) so that I need to

convert that in datetime.

It is saving in sql like this format 02-01-2015

I have written this code in sql

update soINVOICE set INV_DATE =convert(datetime,convert(datetime,INV_DATE ,(105)))

but I am getting this error all the time

The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.

So Please Resolve this error

Posted 2-Aug-15 19:07pm

TarunKumarSusarapu

Updated 2-Aug-15 19:43pm

v3

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2015-08-02T20:08:00

I'd do it in a high level language: C# or similar, and do the conversion there rather than in SQL - you are working with text based dates, and the most likely reason it's giving you problems is that the dates stored are not all valid - that's one of the reasons for always storing then as DATETIME values.

If you do this in a general purpose language, you get a lot better support for errors, and can log or manually correct invalid entries. It's a heck of a lot harder to do that in SQL!

khan aadam · Answer 2 · 2015-08-02T20:39:00

Solution 2

SQL

update soINVOICE set INV_DATE =convert(datetime,convert(varcahr(16),INV_DATE ,(105)))

Posted 2-Aug-15 20:39pm

khan aadam

Abhinav S · Answer 3 · 2015-08-02T20:57:00

Solution 3

DateTime.TryParse[^] and DateTime.ParseExact[^] can help you resolve some of these errors at the front end.

Posted 2-Aug-15 20:57pm

Abhinav S