Friday, October 17, 2008

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

There are some times where database applications give the above error when trying to convert strings to the datetime format in SQL Server.

This error is related to the default language and consequently the dateformat used by the corresponding SQL Server login.

There are two approaches for avoiding/resolving this issue. The first approach is to include the necessary logic in your database application in order not to depend on the default language setting, but use the ISO date format which is: yyyy-mm-dd hh:nn:ss.

The second approach is to change the default language setting for the specific SQL Server login to "us_english".

By executing the following script in SQL Server you get a list with all the logins and among others, the default language names used by these logins. The relevant column name in the results of this script is the "DefLangName":

--Query that changes the default language to "us_english" for a given SQL Server login:
use [master]
EXEC sp_helplogins
GO

If the default language name for the specific login is different than "us_english", and your application's code does not explicitly handle these date-conversion issues, there is the possibility of getting the conversion error when executing your application. You can easily change this setting to "us_english" by executing the below script:

--Query that changes the default language to "us_english" for a given SQL Server login:
use [master]
ALTER LOGIN "LOGIN_NAME" WITH DEFAULT_LANGUAGE = us_english;
GO

* You have to change the "LOGIN_NAME" string to the desired login name for which you would like to change its default language setting.

* You can also change this setting through SQL Server Management Studio.

Concluding, the safest way to handle dateformat data in database applications, is to setup the default language setting for the relevant SQL Server login to "us_english" and use parameterized queries in your source code. To this end, the date formatting will be automatically handled thus avoiding possible conversion errors.

Hope this helps.
[Ad]
Easily secure your SQL Server instances! Try out DBA Security Advisor!
DBA Security Advisor for SQL Server by SQLArtBits
DBA Security Advisor was developed by SQLArtBits. The tool was being carefully developed for an entire year and it contains comprehensive security checks and recommendations based on proven SQL Server security best practices. Feel free to download and use the Community Edition which is free and if you find it useful, you can consider upgrading to the Enterprise Edition!

Artemakis Artemiou [MVP]

Author & Editor

Artemakis Artemiou is a Senior SQL Server Architect, Software Developer and Microsoft Data Platform MVP. He is also an author, regular blogger, president of Cyprus.NET User Group and CY Country leader of INETA-EU. He is also the creator of DBA Security Advisor and In-Memory OLTP Simulator. Artemakis is a frequent guest author of worldwide well-respected online journals where he writes articles focusing on many SQL Server topics.

Reference: The SQL Server and .NET Hub (http://www.sqlnethub.com)

1 comments:

f2KFaMh.qc5_Yyqy0wfV3TTVGk46wg-- said...

Just as a sidenote to this, i'm running SQL Server 2005 SP2 (with the language of the sql account set to British English). I had issues around using the ISO format YYYY-MM-DD. I got the "conversion of char data type" exception with that format when the day was > 12. When changing the language of the sql account to Engligh (us_english) the same query went through fine. However, when i changed my code to format the date into YYYYMMDD the query worked with both languages, so i don't know if this is a SQL bug or what, but i'm using the latter format now.